<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-secure-core.git/meta-integrity, 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>2018-12-08T01:42:55+00:00</updated>
<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>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>meta-integrity: rpm: Add back in required patches for rocko</title>
<updated>2018-07-31T14:48:35+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2018-07-31T14:30:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=5fa9c850bd0b1d4d4cd1ee5604cfe3052035f000'/>
<id>urn:sha1:5fa9c850bd0b1d4d4cd1ee5604cfe3052035f000</id>
<content type='text'>
In 59a9f43b899c ("meta-integrity: Drop RPM patches that are upstream
now") we removed patches to RPM that were not required with a move up to
4.14.0 as they are upstream.  However, rocko ships with an older version
of RPM and still needs these patches.  Add conditional logic to apply
these patches only for rocko.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: Mark as compatible with rocko</title>
<updated>2018-07-25T12:41:35+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2018-07-25T12:26:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=cd40815e69cba65ad8181f4689ff7e26053d28e7'/>
<id>urn:sha1:cd40815e69cba65ad8181f4689ff7e26053d28e7</id>
<content type='text'>
As we also work with the 'rocko' release list that in our
LAYERSERIES_COMPAT.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>util-linux: allow -static linking for switch_root.static</title>
<updated>2018-07-06T06:50:47+00:00</updated>
<author>
<name>Joe Slater</name>
<email>joe.slater@windriver.com</email>
</author>
<published>2018-02-05T22:36:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=4a357121bff4839cb481286f768550d58b36f29c'/>
<id>urn:sha1:4a357121bff4839cb481286f768550d58b36f29c</id>
<content type='text'>
Specify -no-pie to override possible -pie default.

Signed-off-by: Joe Slater &lt;joe.slater@windriver.com&gt;
Signed-off-by: Yi Zhao &lt;yi.zhao@windriver.com&gt;
</content>
</entry>
<entry>
<title>sign_rpm_ext.bbclass: fix check_rpm_public_key racing at recipe parsing time</title>
<updated>2018-05-31T03:26:13+00:00</updated>
<author>
<name>Hongxu Jia</name>
<email>hongxu.jia@windriver.com</email>
</author>
<published>2018-05-31T01:54:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=38ba5938416ba488f10849080a11069242924e89'/>
<id>urn:sha1:38ba5938416ba488f10849080a11069242924e89</id>
<content type='text'>
All recipe will be parsed which caused lockfile of
check_rpm_public_key racing issue.
...
|WARNING: meta-secure-core/meta/recipes-core/images/secure-core-image-initramfs.bb:
oe-core/bitbake/lib/bb/utils.py:400: ResourceWarning: unclosed file
&lt;_io.TextIOWrapper name='tmp-glibc/check_rpm_public_key.lock' mode='a+' encoding='UTF-8'&gt;
...

Refer do_package_write_rpm, add check_rpm_public_key to
prefunc of do_rootfs, only the running image recipe will
invoke check_rpm_public_key.

Signed-off-by: Hongxu Jia &lt;hongxu.jia@windriver.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: add LAYERSERIES_COMPAT</title>
<updated>2018-05-26T00:08:58+00:00</updated>
<author>
<name>Trevor Woerner</name>
<email>twoerner@gmail.com</email>
</author>
<published>2018-05-25T18:44:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=18d65f89333b1a8482aab9183b143d18b44e9057'/>
<id>urn:sha1:18d65f89333b1a8482aab9183b143d18b44e9057</id>
<content type='text'>
see https://patchwork.openembedded.org/patch/140542/

Signed-off-by: Trevor Woerner &lt;twoerner@gmail.com&gt;
</content>
</entry>
<entry>
<title>sign_rpm_ext.bbclass: check rpm public key at image recipe parsing time</title>
<updated>2018-05-23T11:32:55+00:00</updated>
<author>
<name>Hongxu Jia</name>
<email>hongxu.jia@windriver.com</email>
</author>
<published>2018-05-23T09:05:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=7824fbdea866f17bcbf631a028828d93d5d9892c'/>
<id>urn:sha1:7824fbdea866f17bcbf631a028828d93d5d9892c</id>
<content type='text'>
While multiple builds share a common sstate, the latter
build failed to build image which the public key not found.
...
|ERROR: initramfs-ostree-image-1.0-r0 do_rootfs: Importing GPG key failed.
Command 'rpmkeys --root=&lt;path&gt;/rootfs --import &lt;path&gt;/rpm-key' returned 1:
...

The latter build will not regenerate rpm packages and
check_rpm_public_key will not be invoked.

Explicitly invoke check_rpm_public_key at image recipe parsing time,
which make sure gpg public key be imported.

Signed-off-by: Hongxu Jia &lt;hongxu.jia@windriver.com&gt;
</content>
</entry>
<entry>
<title>meta-integrity, meta-signing-key: Populate the secondary keyring</title>
<updated>2018-05-17T12:36:23+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2018-05-17T03:08:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=a8419d577a840ef86bce479af2057e454d8b1bc0'/>
<id>urn:sha1:a8419d577a840ef86bce479af2057e454d8b1bc0</id>
<content type='text'>
Currently we provide a secondary trusted key that is signed by the
primary key.  We do not however DER encode this certificate.  Update
the key-store recipe to also make a DER encoding of this certificate and
include it in the same package as the PEM version of the certificate.
In the IMA init script, if we have any secondary certificate in a DER
encoding, load them into the secondary keyring before we try and load
the IMA keys.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>meta-integrity: init.ima: Switch to using keyctl</title>
<updated>2018-05-17T12:36:23+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2018-05-16T14:31:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=b7b42cdec7b20be00ea2c344189f5924951d3037'/>
<id>urn:sha1:b7b42cdec7b20be00ea2c344189f5924951d3037</id>
<content type='text'>
Rather than parse /proc/keys directly to find out the ID of the keyring
that we're using, let keyctl do this for us.  In order to do that we
need to have /proc available as /proc, so move it around before and
after working with keyctl.

Signed-off-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
</feed>
