<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-secure-core.git, branch thud</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=thud</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-secure-core.git/atom?h=thud'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/'/>
<updated>2021-08-24T01:19:32+00:00</updated>
<entry>
<title>fix sbsigningtool SRC_URI</title>
<updated>2021-08-24T01:19:32+00:00</updated>
<author>
<name>Jonathan Marler</name>
<email>johnnymarler@gmail.com</email>
</author>
<published>2021-08-23T20:54:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=5befefe199892adba78a29f762fd4ad8fb125686'/>
<id>urn:sha1:5befefe199892adba78a29f762fd4ad8fb125686</id>
<content type='text'>
The SRC_URI git://kernel.ubuntu.com/jk/sbsigntool no longer exists. I've updated the SRC_URI to point to the new location.
</content>
</entry>
<entry>
<title>Create the stable branch thud</title>
<updated>2018-12-11T02:10:50+00:00</updated>
<author>
<name>Jia Zhang</name>
<email>zhang.jia@linux.alibaba.com</email>
</author>
<published>2018-12-11T02:10:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=db22483ff3e2b5f70030c12b2d40bcfeae028a32'/>
<id>urn:sha1:db22483ff3e2b5f70030c12b2d40bcfeae028a32</id>
<content type='text'>
And Yi Zhao becomes the maintainer for this branch.

Signed-off-by: Jia Zhang &lt;zhang.jia@linux.alibaba.com&gt;
</content>
</entry>
<entry>
<title>grub-efi: fix the potential uninitialized error for variable 'err'</title>
<updated>2018-12-03T07:12:41+00:00</updated>
<author>
<name>Wenzong Fan</name>
<email>wenzong.fan@windriver.com</email>
</author>
<published>2018-01-30T08:42:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=dba30381528fcf50ac50b15461b00c4f0a280d78'/>
<id>urn:sha1:dba30381528fcf50ac50b15461b00c4f0a280d78</id>
<content type='text'>
Fix the build errors with DEBUG_BUILD enabled:
  grub-core/loader/linux.c: In function 'grub_initrd_load':
  grub-core/loader/linux.c:326:10: error: 'err' may be used \
  uninitialized in this function [-Werror=maybe-uninitialized]

In function grub_initrd_load:
grub_initrd_load (struct grub_linux_initrd_context *initrd_ctx,
          char *argv[], void *target)
{
  [snip]
  grub_err_t err;
  [snip]

  #ifdef GRUB_MACHINE_EFI
      [snip]
      err = grub_verify_file (argv[i]);
      [snip]
  #endif

  [snip]
fail:
  [snip]
  return err;
}

If the GRUB_MACHINE_EFI is not defined, the function would return an
uninitialized value for 'err'. We should initialize it when this
variable is assigned.

Signed-off-by: Wenzong Fan &lt;wenzong.fan@windriver.com&gt;
Signed-off-by: Yi Zhao &lt;yi.zhao@windriver.com&gt;
</content>
</entry>
<entry>
<title>base-files: only apply the bbappend if ima distro flag set</title>
<updated>2018-12-03T07:12: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=22bd7aa878adfc8f7b6c12bc92e441fa3b161e2c'/>
<id>urn:sha1:22bd7aa878adfc8f7b6c12bc92e441fa3b161e2c</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-11-30T05:46:35+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=ca566bb615b781283571653ef86fcd1d21a42f57'/>
<id>urn:sha1:ca566bb615b781283571653ef86fcd1d21a42f57</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-11-30T05:46:35+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=deed416dd82fb85da5a89d80990431fe87fae97b'/>
<id>urn:sha1:deed416dd82fb85da5a89d80990431fe87fae97b</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-11-07T15:40:20+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=627475766502fd1f0c957ec9c6927d18a16b3aa8'/>
<id>urn:sha1:627475766502fd1f0c957ec9c6927d18a16b3aa8</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>mtree: update context of configure.ac-automake-error.patch</title>
<updated>2018-11-07T09:09:00+00:00</updated>
<author>
<name>Kai Kang</name>
<email>kai.kang@windriver.com</email>
</author>
<published>2018-11-07T07:56:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=66d764ad2b4cc372f5ba0c51e1bffe5c670444d7'/>
<id>urn:sha1:66d764ad2b4cc372f5ba0c51e1bffe5c670444d7</id>
<content type='text'>
It shows warning when apply configure.ac-automake-error.patch:

| WARNING: mtree-1.0.3+gitAUTOINC+4f3e901aea-r0 do_patch:
| ...
| Details:
| Applying patch configure.ac-automake-error.patch
| patching file configure.ac
| Hunk #1 succeeded at 4 with fuzz 2 (offset -2 lines).

Update context of configure.ac-automake-error.patch to sync with current
mtree source codes.

Signed-off-by: Kai Kang &lt;kai.kang@windriver.com&gt;
</content>
</entry>
<entry>
<title>key-store: rename ima private key and certificate on target</title>
<updated>2018-11-07T06:22:47+00:00</updated>
<author>
<name>Yunguo Wei</name>
<email>yunguo.wei@windriver.com</email>
</author>
<published>2018-10-26T02:16:42+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=37a59625e5cc1cebb95427fdbc86826e02d7e065'/>
<id>urn:sha1:37a59625e5cc1cebb95427fdbc86826e02d7e065</id>
<content type='text'>
If sample keys are selected, key-store service will deploy IMA private
key during first boot, but beople may be confused if we deploy a sample
private key like "xxx.crt", so this commit is making sure key/cert on
target are consistent with key files on build system.

Signed-off-by: Yunguo Wei &lt;yunguo.wei@windriver.com&gt;
</content>
</entry>
<entry>
<title>meta-signing-key: When deploying keys UEFI keys, deploy DER format</title>
<updated>2018-10-25T15:03:40+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=bf314c0d0c9d38c3d4b8ab4fb0cdfd77cddfa59e'/>
<id>urn:sha1:bf314c0d0c9d38c3d4b8ab4fb0cdfd77cddfa59e</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>
</feed>
