<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-secure-core.git, branch sumo</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=sumo</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-secure-core.git/atom?h=sumo'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/'/>
<updated>2022-02-09T00:58:58+00:00</updated>
<entry>
<title>Updated the URI for Jeremy Kerr's sbsigntools</title>
<updated>2022-02-09T00:58:58+00:00</updated>
<author>
<name>Dimitri Bouras</name>
<email>dimitrios.bouras@gmail.com</email>
</author>
<published>2022-02-08T23:34:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=6dd9a49284bd29754abcb4fd312cdff43d5f3a69'/>
<id>urn:sha1:6dd9a49284bd29754abcb4fd312cdff43d5f3a69</id>
<content type='text'>
Jeremy Kerr's sbsigntools are no longer hosted on git://kernel.ubuntu.com/jk/sbsigntool. A copy exists at git://git.kernel.org/pub/scm/linux/kernel/git/jejb/sbsigntools. This change is required to build meta-secure-core under sumo.</content>
</entry>
<entry>
<title>Update git source URL because of 404 error.</title>
<updated>2021-11-22T09:19:37+00:00</updated>
<author>
<name>tomita</name>
<email>tomita@cyberdefense.jp</email>
</author>
<published>2021-11-07T14:48:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=c9d359ea33552b8f8b4728483100bb8225fe38cd'/>
<id>urn:sha1:c9d359ea33552b8f8b4728483100bb8225fe38cd</id>
<content type='text'>
Signed-off-by: tomita &lt;tomita@cyberdefense.jp&gt;
</content>
</entry>
<entry>
<title>initrdscripts-secure-core: remove /sys and /proc from package</title>
<updated>2021-11-22T09:19:37+00:00</updated>
<author>
<name>tomita</name>
<email>tomita@cyberdefense.jp</email>
</author>
<published>2021-11-07T14:47:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=22ed4822a808dd6ddcf62b550d2bdc85bad91e95'/>
<id>urn:sha1:22ed4822a808dd6ddcf62b550d2bdc85bad91e95</id>
<content type='text'>
The following failure is shown during secure-core-image-initramfs:do_rootfs():

Error: Transaction check error: file /proc conflicts between attempted installs of initrdscripts-secure-core-1.0-r0.corei7_64 and base-files-3.0.14-r89.intel_x86_64 file /sys conflicts between attempted installs of initrdscripts-secure-core-1.0-r0.corei7_64 and base-files-3.0.14-r89.intel_x86_64

So remove /sys and /proc as base-files has already provided them.

Signed-off-by: tomita &lt;tomita@cyberdefense.jp&gt;
</content>
</entry>
<entry>
<title>base-files: only apply the bbappend if ima distro flag set</title>
<updated>2018-12-08T01:42:55+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=1b35fd45a58ef015b52a3df4b39048f2ac1ffbe3'/>
<id>urn:sha1:1b35fd45a58ef015b52a3df4b39048f2ac1ffbe3</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:55+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=41af20a81d06c1c582eb046cf4b85ded27be6dfb'/>
<id>urn:sha1:41af20a81d06c1c582eb046cf4b85ded27be6dfb</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:55+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=f26181d04c26bddeec93fc308ecaba27343ae03d'/>
<id>urn:sha1:f26181d04c26bddeec93fc308ecaba27343ae03d</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:55+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=ff8db97cb8fb890f1cc658fcbff176326c8be13a'/>
<id>urn:sha1:ff8db97cb8fb890f1cc658fcbff176326c8be13a</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:07:35+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=5c56f9534bf20d9c91932ff3870fa2254d44c333'/>
<id>urn:sha1:5c56f9534bf20d9c91932ff3870fa2254d44c333</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 sumo</title>
<updated>2018-09-21T06:26:49+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=ba72aa48fbfb33323e680fcbdd72633bca2cb6ae'/>
<id>urn:sha1:ba72aa48fbfb33323e680fcbdd72633bca2cb6ae</id>
<content type='text'>
The following commits are reverted by the way:

- meta-integrity: rpm: Add back in required patches for rocko (5fa9c85)
- meta-intel-sgx: Initial support of linux-sgx-driver (7d4f711)

The former is applicable to rocko only, and the latter is still experimental.

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:41:05+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=13742554bfd1422ee6708c209aea1acf59525642'/>
<id>urn:sha1:13742554bfd1422ee6708c209aea1acf59525642</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>
</feed>
