<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-secure-core.git/meta-signing-key, 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>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>
<entry>
<title>libsign: Fix build failure with GCC 8.x</title>
<updated>2018-10-08T11:14:22+00:00</updated>
<author>
<name>Yunguo Wei</name>
<email>yunguo.wei@windriver.com</email>
</author>
<published>2018-10-08T08:03:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=45893433ad6a676b8a6f3227ec6f2b1f6663691e'/>
<id>urn:sha1:45893433ad6a676b8a6f3227ec6f2b1f6663691e</id>
<content type='text'>
Signed-off-by: Yunguo Wei &lt;yunguo.wei@windriver.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: update LAYERSERIES_COMPAT `sumo' -&gt; `thud'</title>
<updated>2018-10-08T06:47:47+00:00</updated>
<author>
<name>Hongxu Jia</name>
<email>hongxu.jia@windriver.com</email>
</author>
<published>2018-10-07T14:29:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=c1a543fc998597acc1763ccbc5e8b3c19da50f70'/>
<id>urn:sha1:c1a543fc998597acc1763ccbc5e8b3c19da50f70</id>
<content type='text'>
Since `9ec5a8a layer.conf: Drop sumo from LAYERSERIES_CORENAMES' and
`9867924 layer.conf: Add thud to LAYERSERIES_CORENAMES' applied in oe-core,
update LAYERSERIES_COMPAT `sumo' -&gt; `thud'

Signed-off-by: Hongxu Jia &lt;hongxu.jia@windriver.com&gt;
</content>
</entry>
<entry>
<title>Clean up the stuffs for stable branches</title>
<updated>2018-09-21T01:21:37+00:00</updated>
<author>
<name>Jia Zhang</name>
<email>zhang.jia@linux.alibaba.com</email>
</author>
<published>2018-09-21T01:21:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=139a9b656d789db5a3caa40fe719e5e736add9da'/>
<id>urn:sha1:139a9b656d789db5a3caa40fe719e5e736add9da</id>
<content type='text'>
The following commits are reverted by the way:

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

Because they are only applicable to rocko.

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-18T03:21:43+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=f450605d48c82a49c8bde9e6328b9a3999d77fcf'/>
<id>urn:sha1:f450605d48c82a49c8bde9e6328b9a3999d77fcf</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-18T03:21:41+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=be735c09cb4785f3a8fac834995fa01d774e0428'/>
<id>urn:sha1:be735c09cb4785f3a8fac834995fa01d774e0428</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>key-store: fix incorrect postpone to first boot</title>
<updated>2018-09-05T10:53:58+00:00</updated>
<author>
<name>Hongxu Jia</name>
<email>hongxu.jia@windriver.com</email>
</author>
<published>2018-09-05T07:53:08+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=13ae9807965013dac84d188e0e70b431fbf0cd23'/>
<id>urn:sha1:13ae9807965013dac84d188e0e70b431fbf0cd23</id>
<content type='text'>
After postinst was executed at do_rootfs successfully,
there will be no first boot to redo.

Since `229f4e9 package.bbclass: add support for
pkg_postinst_ontarget()' applied in oe-core, use
pkg_postinst_ontarget to instead.

Signed-off-by: Hongxu Jia &lt;hongxu.jia@windriver.com&gt;
</content>
</entry>
<entry>
<title>libsign: Enable nativesdk support</title>
<updated>2018-08-25T00:14:56+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2018-08-22T02:47:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-secure-core.git/commit/?id=93bba331667eccc67324860fecc51ca0a89a6535'/>
<id>urn:sha1:93bba331667eccc67324860fecc51ca0a89a6535</id>
<content type='text'>
Bump up to the current top of libsign so that we can easily get a copy
of selsign that can be put into an SDK.

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