live-boot (1:20230131)
[PTS] [DDPO]
COMMITS: VCS has seen 3 commits since the debian/1%20230131 tag
- Git: https://salsa.debian.org/live-team/live-boot.git
-
- Branch: master
- Path: debian/changelog
- Repo size: 5513216
- Browser: https://salsa.debian.org/live-team/live-boot
- Last scan: 2023-05-31 04:07:23+00
- Next scan: 2023-06-07 21:11:00+00
- Merge requests: 6
- CI pipeline status: failed
- Debian changelog in Git:
live-boot (1:20230131) unstable; urgency=medium
[ Thore Sommer ]
* set redirect=on for overlayfs unions
* fix dm-verity installation for non merged /bin and /usr/bin (Closes:
#1010951)
-- Luca Boccassi <bluca@debian.org> Tue, 31 Jan 2023 16:30:52 +0000
- This branch is 3 commits ahead of tag debian/1%20230131
- Git log:
commit 51b57c3347366b05cb50b1bb411d6c6ecc998d04
Merge: 082e7a9 d2be333
Author: Luca Boccassi <bluca@debian.org>
Date: Sat Mar 18 16:45:32 2023 +0000
Merge branch 'luks-label' into 'master'
Introduce lukslabel option + fix for is_active_luks_mapping()
See merge request live-team/live-boot!44
commit d2be333ca62e98c5fdd0b4c618600e5483bac8b3
Author: Thore Sommer <debian@thson.de>
Date: Sat Mar 18 15:49:54 2023 +0200
Introduce lukslabel option
When "lukslabel" is set for persistence-encryption then live-boot only
tries to open containers that have the label "persistence" set. It
takes precedence over the "luks" option.
The behavior of the "luks" option is to prompt the user to open any LUKS
container. This was required for LUKS1 because it did not support labels,
but LUKS2 does. On systems were there are multiple encrypted containers
this is not ideal, because for users it is not clear why they should
decrypt their internal hard drive to boot a live system.
commit 769531e47b3649d6007c6b374723cfaf862a925b
Author: Thore Sommer <debian@thson.de>
Date: Sat Mar 18 15:46:25 2023 +0200
luks: is_active_luks_mapping() check explicitly for type
cryptsetup status also works on other device mapper devices that are not
LUKS or LUKS2.