<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-security.git/meta-integrity, branch master-next</title>
<subtitle>Mirror of git.yoctoproject.org/meta-security.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-security.git/atom?h=master-next</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-security.git/atom?h=master-next'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/'/>
<updated>2026-03-22T14:24:23+00:00</updated>
<entry>
<title>layer.conf: Update to wrynose (6.0) release</title>
<updated>2026-03-22T14:24:23+00:00</updated>
<author>
<name>Marta Rybczynska</name>
<email>marta.rybczynska@ygreky.com</email>
</author>
<published>2026-03-19T13:12:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=8028c573db6923525c2918724f2bd36d4a420e0b'/>
<id>urn:sha1:8028c573db6923525c2918724f2bd36d4a420e0b</id>
<content type='text'>
Update LAYERSERIES_COMPAT in all layer.conf files with the exception
of meta-parsec to wrynose.  For meta-parsec, added wrynose to the list
of supported versions.

Signed-off-by: Marta Rybczynska &lt;marta.rybczynska@ygreky.com&gt;
</content>
</entry>
<entry>
<title>ima-evm-utils: remove unnecessary FILESEXTRAPATHS tweak</title>
<updated>2025-11-13T20:03:36+00:00</updated>
<author>
<name>Scott Murray</name>
<email>scott.murray@konsulko.com</email>
</author>
<published>2025-11-13T20:03:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=5770a76fc0d78a645ab254979986f572fd18b3ec'/>
<id>urn:sha1:5770a76fc0d78a645ab254979986f572fd18b3ec</id>
<content type='text'>
It was pointed out that the recipe was wrongly doing
FILESEXTRAPATHS:append, but on inspection the recipe does
not need it at all, so just remove.

Reported-by: Robert P. J. Day &lt;rpjday@crashcourse.ca&gt;
Signed-off-by: Scott Murray &lt;scott.murray@konsulko.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: Update to whinlatter (5.3) release</title>
<updated>2025-07-04T16:41:20+00:00</updated>
<author>
<name>Scott Murray</name>
<email>scott.murray@konsulko.com</email>
</author>
<published>2025-07-02T22:38:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=ea67ceefdca42da806f3312c6703eff769463b8b'/>
<id>urn:sha1:ea67ceefdca42da806f3312c6703eff769463b8b</id>
<content type='text'>
Update LAYERSERIES_COMPAT in all layer.conf files with the exception
of meta-parsec to whinlatter.  For meta-parsec, whinlatter has been
added, and the EOL releases removed, as an initial update.

Signed-off-by: Scott Murray &lt;scott.murray@konsulko.com&gt;
</content>
</entry>
<entry>
<title>Update maintainers</title>
<updated>2025-06-27T21:16:05+00:00</updated>
<author>
<name>Scott Murray</name>
<email>scott.murray@konsulko.com</email>
</author>
<published>2025-06-27T18:46:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=ebe9234fb8867d5be6916b52b54e24f191f5fcab'/>
<id>urn:sha1:ebe9234fb8867d5be6916b52b54e24f191f5fcab</id>
<content type='text'>
Add Marta and myself as maintainers for meta-security and the other
embedded layers that Armin had been maintaining.  To avoid Armin
getting bugged about individual recipes, set the RECIPE_MAINTAINER
variables to myself for now as a starting point that can be adjusted
as things get more settled.

Signed-off-by: Scott Murray &lt;scott.murray@konsulko.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>Remove self as Maintainer</title>
<updated>2025-06-23T20:14:41+00:00</updated>
<author>
<name>Armin Kuster</name>
<email>akuster808@gmail.com</email>
</author>
<published>2025-06-23T20:14:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=c5ce0b7e469fbee4ca630d3adefba63e3fefb3fe'/>
<id>urn:sha1:c5ce0b7e469fbee4ca630d3adefba63e3fefb3fe</id>
<content type='text'>
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>meta-integrity: Enable choice of creating IMA signatures or hashes</title>
<updated>2025-03-12T19:31:15+00:00</updated>
<author>
<name>Stefan Berger</name>
<email>stefanb@linux.ibm.com</email>
</author>
<published>2025-02-06T20:54:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=a76a5c51283b9d361caf514dc5cdebd72b5b4ca1'/>
<id>urn:sha1:a76a5c51283b9d361caf514dc5cdebd72b5b4ca1</id>
<content type='text'>
When IMA and EVM are used for file appraisal then EVM verifies the
signature stored in security.evm. This signature covers file metadata
(uid, gid, mode bits, etc.) as well as the security.ima xattr.
Therefore, it is sufficient that only files' hashes are stored in
security.ima. This also leads to slight performance improvements
since IMA appraisal will then only verify that a file's hash matches
the expected hash stored in security.ima. EVM will ensure that the
signature over all the file metadata and security.ima xattr is
correct. Therefore, give the user control over whether to store file
signatures (--imasig) in ima.security or hashes (--imahash) by
setting the option in IMA_EVM_IMA_XATTR_OPT.

Only test-verify an IMA signature if --imasig is used as the option.

Signed-off-by: Stefan Berger &lt;stefanb@linux.ibm.com&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>meta-security: Remove True option to getVar calls</title>
<updated>2025-02-03T02:11:12+00:00</updated>
<author>
<name>akash hadke</name>
<email>akash.hadke27@gmail.com</email>
</author>
<published>2025-01-09T10:43:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=8fcbc47b9c56fe405a7a6d51ff0d8e2b756818ea'/>
<id>urn:sha1:8fcbc47b9c56fe405a7a6d51ff0d8e2b756818ea</id>
<content type='text'>
getVar() now defaults to expanding by default, thus remove the True
option from getVar() calls with a regex search and replace.

Signed-off-by: Akash Hadke &lt;akash.hadke27@gmail.com&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>oeqa runtime ima.py: skip without "integrity" in DISTRO_FEATURES</title>
<updated>2024-12-27T16:28:23+00:00</updated>
<author>
<name>Mikko Rapeli</name>
<email>mikko.rapeli@linaro.org</email>
</author>
<published>2024-12-20T14:04:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=1f7cc51443cb6baa1de519df1a9c570b3f5cae2a'/>
<id>urn:sha1:1f7cc51443cb6baa1de519df1a9c570b3f5cae2a</id>
<content type='text'>
ima and meta-integrity are not enabled without and the test fails.

Signed-off-by: Mikko Rapeli &lt;mikko.rapeli@linaro.org&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: Update to walnascar (5.2) layer/release series</title>
<updated>2024-11-25T01:15:36+00:00</updated>
<author>
<name>Armin Kuster</name>
<email>akuster808@gmail.com</email>
</author>
<published>2024-10-05T16:33:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=0055dfe35d98bcfb11cb649c89a868ad9c163497'/>
<id>urn:sha1:0055dfe35d98bcfb11cb649c89a868ad9c163497</id>
<content type='text'>
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>layer.conf: Update to styhead release name series</title>
<updated>2024-09-15T15:27:10+00:00</updated>
<author>
<name>Armin Kuster</name>
<email>akuster808@gmail.com</email>
</author>
<published>2024-09-15T15:27:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=5e742d7fb09f63c558738dc9ec728dfdc624cec4'/>
<id>urn:sha1:5e742d7fb09f63c558738dc9ec728dfdc624cec4</id>
<content type='text'>
few more layers to fixup

Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
</feed>
