<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-security.git/classes, 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-05-17T14:45:41+00:00</updated>
<entry>
<title>aide-base.bbclass: correct STAGING_AIDE_DIR</title>
<updated>2026-05-17T14:45:41+00:00</updated>
<author>
<name>Li Zhou</name>
<email>li.zhou@windriver.com</email>
</author>
<published>2026-04-27T02:48:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=b4c43ad77ad7eedab05d48dcbd32e4ef96b21c83'/>
<id>urn:sha1:b4c43ad77ad7eedab05d48dcbd32e4ef96b21c83</id>
<content type='text'>
Fix the typo "aida" to "aide" in STAGING_AIDE_DIR.

Signed-off-by: Li Zhou &lt;li.zhou@windriver.com&gt;
Signed-off-by: Scott Murray &lt;scott.murray@konsulko.com&gt;
</content>
</entry>
<entry>
<title>dm-verity-img.bbclass: filter units from value part</title>
<updated>2026-01-16T21:25:02+00:00</updated>
<author>
<name>Stephan Wurm</name>
<email>stephan.wurm@a-eberle.de</email>
</author>
<published>2026-01-07T13:37:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=9e6d962250aab6e5319215f15b0201ef233c46cd'/>
<id>urn:sha1:9e6d962250aab6e5319215f15b0201ef233c46cd</id>
<content type='text'>
This is necessary for cryptsetup starting from v2.8.0 which introduced
"[units]" in its output breaking the parsing of veritysetup output.

VERITY header information for image-poky-20250701085433.squashfs-zst.verity.
UUID:                   5dc16c55-79b8-4988-9d79-900f8e143f98
Hash type:              1
Data blocks:            40091
Data block size:        4096 [bytes]
Hash blocks:            318
Hash block size:        4096 [bytes]
Hash algorithm:         sha256
Salt:                   f670bf67a32f4f5a22e052d7bf84830f8d35ea24e2d52f585f6275207899153b
Root hash:              a7eab55b7933e347650671611e4b2a10571f2a28a1fb0fc8eae409f7a0d86693

This extends the value filter to remove the "[units]" from the .env file,
while retaining compatibility to older cryptsetup releases.

Signed-off-by: Stephan Wurm &lt;stephan.wurm@a-eberle.de&gt;
Signed-off-by: Scott Murray &lt;scott.murray@konsulko.com&gt;
</content>
</entry>
<entry>
<title>dm-verity-img.bbclass: set sparse as "never" during initial file copy</title>
<updated>2025-03-12T19:31:15+00:00</updated>
<author>
<name>Lorenzo Arena</name>
<email>arena.lor@gmail.com</email>
</author>
<published>2025-02-17T14:54:20+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=674f1e3367c7cfb606047b2050338c725ba2eca2'/>
<id>urn:sha1:674f1e3367c7cfb606047b2050338c725ba2eca2</id>
<content type='text'>
This is needed when a verity image is used in conjunction with tools
like a WIC and a bmap file, as avoiding writing "sparse" sectors
can result in errors in the signature verification.

Signed-off-by: Lorenzo Arena &lt;arena.lor@gmail.com&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>dm-verity: set staging correctly in case basename has changed</title>
<updated>2024-12-16T17:49:13+00:00</updated>
<author>
<name>Louis Rannou</name>
<email>louis.rannou@non.se.com</email>
</author>
<published>2024-05-20T19:33:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=8c9cdd60e429025ad75827eca08d37ef2725b832'/>
<id>urn:sha1:8c9cdd60e429025ad75827eca08d37ef2725b832</id>
<content type='text'>
Fix the verity class when the IMAGE_BASENAME has changed. Prefer DM_VERITY_IMAGE
for staging env and wic fragment so it matchs what is used in the
dm-verity-image-initramfs and the base wks systemd-bootdisk-dmverity.wks.in.

Signed-off-by: Louis Rannou &lt;louis.rannou@non.se.com&gt;
Signed-off-by: Louis Rannou &lt;louis.rannou@syslinbit.com&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>dm-verity-img.bbclass: add DM_VERITY_SETUP_ARGS</title>
<updated>2024-12-16T17:49:04+00:00</updated>
<author>
<name>gr embeter</name>
<email>grembeter=gmail.com@lists.yoctoproject.org</email>
</author>
<published>2024-11-09T11:31:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=29d46054c2a3c71ae1ad164a6f32bd6ecbe1b07b'/>
<id>urn:sha1:29d46054c2a3c71ae1ad164a6f32bd6ecbe1b07b</id>
<content type='text'>
Useful to pass additional arguments to veritysetup, for example
'--no-superblock' to make system less vulnerable to certain types of
attacks and data maniputaion on the disk.

Signed-off-by: Grygorii Tertychnyi &lt;grembeter@gmail.com&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>dm-verity: Set the IMAGE_FSTYPES correctly when dm-verity is enabled</title>
<updated>2024-03-27T16:36:58+00:00</updated>
<author>
<name>Kevin Hao</name>
<email>kexin.hao@windriver.com</email>
</author>
<published>2024-02-22T01:21:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=d80cd2ba6a3ef850cef12578671a5b17d86d3e7c'/>
<id>urn:sha1:d80cd2ba6a3ef850cef12578671a5b17d86d3e7c</id>
<content type='text'>
After the using inherit_defer for the image classes in oe-core commit
451363438d38 ("classes/recipes: Switch to use inherit_defer"),
the using of anonymous python function in dm-verity-img.bbclass to
set the IMAGE_FSTYPES doesn't work anymore. The reason is that
image.bbclass also use anonymous python function to add the do_image_xxx
task for the corresponding filesystem type. The anonymous function in
dm-verity-img.bbclass is evaluated much later than the one in
image.bbclass. Then the task such as do_image_vhash will not be added
as we expect. So we choose to use "+=" to set the IMAGE_FSTYPES.

The populate_sdk_ext.bbclass may generate a dependency list like below:
  core-image-minimal.do_sdk_depends -&gt; lib32-core-image-minimal.do_image_vhash

So we also need to make sure the do_image_vhash task for the multilib
filesystem is added.

Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>dm-verity: Adjust the image names according to the oe-core change</title>
<updated>2024-03-27T16:36:58+00:00</updated>
<author>
<name>Kevin Hao</name>
<email>kexin.hao@windriver.com</email>
</author>
<published>2024-02-22T01:21:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=7b951e3900943b5f4a05a0c06cdff6bd29b4fa00'/>
<id>urn:sha1:7b951e3900943b5f4a05a0c06cdff6bd29b4fa00</id>
<content type='text'>
After the oe-core commit 26d97acc7137 ("image-artifact-names: include
${IMAGE_NAME_SUFFIX} directly in both ${IMAGE_NAME} and
${IMAGE_LINK_NAME}"), the image names have changed from
  core-image-minimal-qemux86-64-20230307181808.rootfs.ext4
  core-image-minimal-qemux86-64.ext4
to
  core-image-minimal-qemux86-64.rootfs-20230307181456.ext4
  core-image-minimal-qemux86-64.rootfs.ext4

Adjust the images name used by dm-verity according to this change.

Signed-off-by: Kevin Hao &lt;kexin.hao@windriver.com&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>dm-verity-img.bbclass: add DM_VERITY_DEPLOY_DIR</title>
<updated>2023-12-29T14:09:30+00:00</updated>
<author>
<name>Mikko Rapeli</name>
<email>mikko.rapeli@linaro.org</email>
</author>
<published>2023-12-21T07:57:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=73e03651ef78d42577e052d7abfc13a9a36b3cbd'/>
<id>urn:sha1:73e03651ef78d42577e052d7abfc13a9a36b3cbd</id>
<content type='text'>
If image recipe A wants to embed another image B which used
dm-verity-img.bbclass and generated the .wks file, then
recipe B must deploy everything to IMGDEPLOYDIR but recipe A
finds the output from DM_VERITY_DEPLOY_DIR = "${DEPLOY_DIR_IMAGE}".

Now both A and B images can use dm-verity-img.bbclass.

Signed-off-by: Mikko Rapeli &lt;mikko.rapeli@linaro.org&gt;
Reviewed-by: Erik Schilling &lt;erik.schilling@linaro.org&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>dm-verity-img.bbclass: remove IMAGE_NAME_SUFFIX</title>
<updated>2023-12-29T14:09:30+00:00</updated>
<author>
<name>Erik Schilling</name>
<email>erik.schilling@linaro.org</email>
</author>
<published>2023-12-21T07:57:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=fd295b2c28219a0cd53087e7ff96edecd9b23d9d'/>
<id>urn:sha1:fd295b2c28219a0cd53087e7ff96edecd9b23d9d</id>
<content type='text'>
It is embedded into IMAGE_NAME since poky master branch commit
6f6c79029bc2020907295858449c725952d560a1

Signed-off-by: Mikko Rapeli &lt;mikko.rapeli@linaro.org&gt;
Signed-off-by: Erik Schilling &lt;erik.schilling@linaro.org&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
<entry>
<title>dm-verity-img.bbclass: use bc-native</title>
<updated>2023-12-29T14:09:30+00:00</updated>
<author>
<name>Erik Schilling</name>
<email>erik.schilling@linaro.org</email>
</author>
<published>2023-12-21T07:57:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-security.git/commit/?id=57723ce65ebf4c8647fcf94e139c56cc4634913f'/>
<id>urn:sha1:57723ce65ebf4c8647fcf94e139c56cc4634913f</id>
<content type='text'>
Build host may not have bc.

Signed-off-by: Mikko Rapeli &lt;mikko.rapeli@linaro.org&gt;
Signed-off-by: Erik Schilling &lt;erik.schilling@linaro.org&gt;
Signed-off-by: Armin Kuster &lt;akuster808@gmail.com&gt;
</content>
</entry>
</feed>
