<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-secure-core.git, branch rocko</title>
<subtitle>Mirror of github.com/jiazhang0/meta-secure-core.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-secure-core.git/atom?h=rocko</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-secure-core.git/atom?h=rocko'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/'/>
<updated>2018-12-08T01:42:41+00:00</updated>
<entry>
<title>base-files: only apply the bbappend if ima distro flag set</title>
<updated>2018-12-08T01:42:41+00:00</updated>
<author>
<name>Yi Zhao</name>
<email>yi.zhao@windriver.com</email>
</author>
<published>2017-10-13T00:56:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=5209d236d27253087a2cb7a1b66546092d3a13f9'/>
<id>urn:sha1:5209d236d27253087a2cb7a1b66546092d3a13f9</id>
<content type='text'>
When the meta-integrity layer is included but feature ima is not set, we
would get the following error when the system startup:

  qemux86-64 systemd-remount-fs[81]: mount: /sys/kernel/security: mount point does not exist.
  qemux86-64 systemd-remount-fs[81]: /bin/mount for /sys/kernel/security exited with exit status 32.

Rename base-files_%.bbappend to base-files-integrity.inc and add a new
bbappend. Make sure this piece of code should be applied only if the ima
feature is set.

Signed-off-by: Yi Zhao &lt;yi.zhao@windriver.com&gt;
</content>
</entry>
<entry>
<title>kernel-initramfs: only apply the bbappend if efi-secure-boot distro flag set</title>
<updated>2018-12-08T01:42:41+00:00</updated>
<author>
<name>Yi Zhao</name>
<email>yi.zhao@windriver.com</email>
</author>
<published>2018-11-30T01:47:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=eed5579529af727139c2c5166a4b5504b5cdb5c3'/>
<id>urn:sha1:eed5579529af727139c2c5166a4b5504b5cdb5c3</id>
<content type='text'>
When the meta-efi-secure-boot layer is included but feature
efi-secure-boot is not set. We got the following error with
kernel-initramfs building:

ERROR: kernel-initramfs-1.0-r0 do_deploy: Function failed: do_deploy (log file is located at /buildarea/build/tmp/work/genericx86_64-poky-linux/kernel-initramfs/1.0-r0/temp/log.do_deploy.16995)
ERROR: Logfile of failure stored in: /buildarea/build/tmp/work/genericx86_64-poky-linux/kernel-initramfs/1.0-r0/temp/log.do_deploy.16995
Log data follows:
| DEBUG: Executing python function sstate_task_prefunc
| DEBUG: Python function sstate_task_prefunc finished
| DEBUG: Executing shell function do_deploy
| install: cannot stat '/buildarea/build/tmp/work/genericx86_64-poky-linux/kernel-initramfs/1.0-r0/image/boot/*.p7b': No such file or directory
| WARNING: /buildarea/build/tmp/work/genericx86_64-poky-linux/kernel-initramfs/1.0-r0/temp/run.do_deploy.16995:1 exit 1 from 'install -m 0644 ${SIG} /buildarea/build/tmp/work/genericx86_64-poky-linux/kernel-initramfs/1.0-r0/deploy-kernel-initramfs'
| ERROR: Function failed: do_deploy (log file is located at /buildarea/build/tmp/work/genericx86_64-poky-linux/kernel-initramfs/1.0-r0/temp/log.do_deploy.16995)
ERROR: Task (/buildarea/poky/meta-secure-core/meta/recipes-core/images/kernel-initramfs.bb:do_deploy) failed with exit code '1'

Rename kernel-initramfs.bbappend to kernel-initramfs-efi-secure-boot.inc
and add a new bbappend. Make sure this piece of code should be applied
only if the efi-secure-boot feature is set.

Signed-off-by: Yi Zhao &lt;yi.zhao@windriver.com&gt;
</content>
</entry>
<entry>
<title>kernel-initramfs: fix inconsistent indentation</title>
<updated>2018-12-08T01:42:41+00:00</updated>
<author>
<name>Yi Zhao</name>
<email>yi.zhao@windriver.com</email>
</author>
<published>2018-11-30T01:11:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=4e5557547b81ac408463c4c9f80e92b6bb1392d1'/>
<id>urn:sha1:4e5557547b81ac408463c4c9f80e92b6bb1392d1</id>
<content type='text'>
Use spaces consistently to indent do_install()

Signed-off-by: Yi Zhao &lt;yi.zhao@windriver.com&gt;
</content>
</entry>
<entry>
<title>meta-efi-secure-boot: Ensure openssl-native exists when we need it</title>
<updated>2018-12-08T01:42:41+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2018-11-07T12:46:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=4dd6fcc736fcf12a499b338a114ec1499b458b91'/>
<id>urn:sha1:4dd6fcc736fcf12a499b338a114ec1499b458b91</id>
<content type='text'>
In order to deploy our secure boot keys in DER format we need to use
openssl.  This must be listed in our DEPENDS line in order for the
sysroot to be populated correctly when we run do_sign.  Also drop the
explicit fakeroot on our empty grub-efi do_sign as we may not have
globally populated virtual/fakeroot-native at that point in time.

Fixes: 92316d4b402b ("meta-signing-key: When deploying keys UEFI keys, deploy DER format")
Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>meta-signing-key: When deploying keys UEFI keys, deploy DER format</title>
<updated>2018-10-25T15:06:56+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2018-10-25T14:37:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=0011b44671ddbbcb58cca426e3fa8a88cd4c9711'/>
<id>urn:sha1:0011b44671ddbbcb58cca426e3fa8a88cd4c9711</id>
<content type='text'>
Generally speaking, for firmware to import PK/KEK/DB keys they need to
be in the binary "DER" format and typically have the "cer" file
extension.  When deploying our keys, convert what we have to that format
and deploy as well for ease of use.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>Maintain the stable branch rocko</title>
<updated>2018-09-21T07:20:23+00:00</updated>
<author>
<name>Jia Zhang</name>
<email>zhang.jia@linux.alibaba.com</email>
</author>
<published>2018-09-20T14:08:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=1423a3c5c594fb5b4f6131a42c8d3e243d4958b8'/>
<id>urn:sha1:1423a3c5c594fb5b4f6131a42c8d3e243d4958b8</id>
<content type='text'>
The modifications based on the following commits are made by the way:

- seloader: Fix building for rocko (bc6bbe2)
- meta-integrity: rpm: Add back in required patches for rocko (5fa9c85)

Because the sanity check for rocko now becomes unnecessary.

In addition, the meta-intel-sgx is removed because it is still
experimental.

- meta-intel-sgx: Initial support of linux-sgx-driver (7d4f711)

Signed-off-by: Jia Zhang &lt;zhang.jia@linux.alibaba.com&gt;
</content>
</entry>
<entry>
<title>libsign: Fix build faiure due to -fstack-protector-strong</title>
<updated>2018-09-20T14:10:48+00:00</updated>
<author>
<name>Jia Zhang</name>
<email>zhang.jia@linux.alibaba.com</email>
</author>
<published>2018-09-18T01:36:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=ab99b6a8920a8c40c681e7b6d5d7bed86514cba3'/>
<id>urn:sha1:ab99b6a8920a8c40c681e7b6d5d7bed86514cba3</id>
<content type='text'>
SECURITY_LDFLAGS includes -fstack-protector-strong which cannot work
with CCLD. To work around this issue, filter out it from LDFLAGS.

Signed-off-by: Jia Zhang &lt;zhang.jia@linux.alibaba.com&gt;
</content>
</entry>
<entry>
<title>libsign: Update to the latest</title>
<updated>2018-09-20T14:10:31+00:00</updated>
<author>
<name>Jia Zhang</name>
<email>zhang.jia@linux.alibaba.com</email>
</author>
<published>2018-09-18T01:35:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=72ba29f29541baf05b56885efd277b4ee251f582'/>
<id>urn:sha1:72ba29f29541baf05b56885efd277b4ee251f582</id>
<content type='text'>
- Use CCLD to build executable and library.

Signed-off-by: Jia Zhang &lt;zhang.jia@linux.alibaba.com&gt;
</content>
</entry>
<entry>
<title>cryptfs-tpm2: Fix build faiure due to -fstack-protector-strong</title>
<updated>2018-09-17T13:31:31+00:00</updated>
<author>
<name>Jia Zhang</name>
<email>zhang.jia@linux.alibaba.com</email>
</author>
<published>2018-09-17T13:31:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=74af5e364470df8793c4110f5f2c3b9bd3337fd2'/>
<id>urn:sha1:74af5e364470df8793c4110f5f2c3b9bd3337fd2</id>
<content type='text'>
SECURITY_LDFLAGS includes -fstack-protector-strong which cannot work
with CCLD. To work around this issue, filter out it from LDFLAGS.

Signed-off-by: Jia Zhang &lt;zhang.jia@linux.alibaba.com&gt;
</content>
</entry>
<entry>
<title>cryptfs-tpm2: Update to the latest</title>
<updated>2018-09-17T13:29:52+00:00</updated>
<author>
<name>Jia Zhang</name>
<email>zhang.jia@linux.alibaba.com</email>
</author>
<published>2018-09-17T13:29:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=b3f12e7803ff2acd48b0d450de3325792cf73134'/>
<id>urn:sha1:b3f12e7803ff2acd48b0d450de3325792cf73134</id>
<content type='text'>
- Follow up the regular way to include header file.
- Use CCLD to build executable and library.

Signed-off-by: Jia Zhang &lt;zhang.jia@linux.alibaba.com&gt;
</content>
</entry>
</feed>
