Bug#849400: debian-installer: LUKS on rootfs and boot

Jinesh Choksi (2023-07-29): > - cryptsetup luksFormat --type luks1 /dev/sda2 As mentioned in various other places, first we need to teach GRUB about argon2i(d), then we can think about enabling cryptodisk support. Also, we need a plan for the GRUB-to-Linux handover. Ugly PoC for the first

Bug#849400: debian-installer: LUKS on rootfs and boot

Thanks Jinesh - one question in particular inline below: On Sat, 29 Jul 2023 at 01:29, Jinesh Choksi wrote: > > > > Can you provide a series of steps to replicate the failure case reported in > > this bug? > > > Reproduction Steps > > - Boot using debian-12.1.0-amd64-netinst.iso in a VM > > - At

Bug#849400: debian-installer: LUKS on rootfs and boot

> Can you provide a series of steps to replicate the failure case reported in > this bug? Reproduction Steps - Boot using debian-12.1.0-amd64-netinst.iso in a VM - At the Grub boot menu, select Advanced options > Expert Install - Go through the following install steps using defaults or as

Bug#849400: debian-installer: LUKS on rootfs and boot

Package: debian-installer Followup-For: Bug #849400 X-Debbugs-Cc: jin...@onelittlehope.com Hi Jinesh, Can you provide a series of steps to replicate the failure case reported in this bug? I'll try to find time within the next two weeks to confirm the results that you and others have seen here,

Bug#849400: debian-installer: LUKS on rootfs and boot

Jinesh Choksi (2023-07-03): > - This bug was raised in 2016. > > - Grub2 added support for accessing LUKS1 partitions in 2011. > > - Between 2016 and 2019 (when cryptsetup defaulted to luks2 - > https://gitlab.com/cryptsetup/cryptsetup/-/commit/ae90497762bc4e3f04064e0ebbbde8c64bf27c4a) > the

Bug#849400: debian-installer: LUKS on rootfs and boot

On 2023-07-03 00:57 +01:00 BST, "Cyril Brulebois" wrote: > Hi, > > Jinesh Choksi (2023-07-02): >> The issue is this block of code: >> https://salsa.debian.org/installer-team/partman-crypto/-/blob/master/check.d/crypto_check_mountpoints#L94-102 >> >> This 17 year old "Check - Is there a /boot

Bug#849400: debian-installer: LUKS on rootfs and boot

Hi, Jinesh Choksi (2023-07-02): > The issue is this block of code: > https://salsa.debian.org/installer-team/partman-crypto/-/blob/master/check.d/crypto_check_mountpoints#L94-102 > > This 17 year old "Check - Is there a /boot partition for encrypted > root?" is no longer valid. It is. > Grub2

Bug#849400: debian-installer: LUKS on rootfs and boot

Hi I too encountered difficulty with trying to install the entire system (including /boot) on one encrypted partition. The issue is this block of code: https://salsa.debian.org/installer-team/partman-crypto/-/blob/master/check.d/crypto_check_mountpoints#L94-102 This 17 year old "Check - Is

Bug#849400: debian-installer: LUKS on rootfs and boot

This problem still persists, on DI Buster Alpha 2 and Alpha 3. Working around this even as an expert is rather cumbersome; one has to play with the various menu options, partially configuring disks/partitions etc., to load the necessary cryptsetup components (and dependencies, like awk for

Bug#849400: debian-installer: LUKS on rootfs and boot

On Wed, Sep 27, 2017 at 01:47:52PM +0200, Ben Hutchings wrote: > DO NOT use a fat32 partition for /boot! > > It will appear to work, but the first upgrade of a package that > installs into /boot will fail because dpkg cannot create a hard link > there. Maybe /boot/efi was what was meant. --

Bug#849400: debian-installer: LUKS on rootfs and boot

Thanks Ben, that's reasonable justification. On Wed, Sep 27, 2017 at 9:47 PM, Ben Hutchings wrote: > On Wed, 2017-09-27 at 09:21 +1000, Julian 1 wrote: > > I am affected by this as well. > > > > Googling shows shows people experimenting with workarounds - creating an > >

Bug#849400: debian-installer: LUKS on rootfs and boot

On Wed, 2017-09-27 at 09:21 +1000, Julian 1 wrote: > I am affected by this as well. > > Googling shows shows people experimenting with workarounds - creating an > additional unencrypted /boot partition independent of the unencrypted EFI > partition. > > This is overly complicated when the

Bug#849400: debian-installer: LUKS on rootfs and boot

I am affected by this as well. Googling shows shows people experimenting with workarounds - creating an additional unencrypted /boot partition independent of the unencrypted EFI partition. This is overly complicated when the subsequent install workflow already does the correct thing - in

Bug#849400: debian-installer: LUKS on rootfs and boot

On Tuesday 27 December 2016 11:58:53 Pali Rohár wrote: > On Monday 26 December 2016 18:58:04 Cyril Brulebois wrote: > > Hi, > > > > Pali Rohár (2016-12-26): > > > Package: debian-installer > > > Severity: normal > > > > > > Dear Maintainer, > > > > > > Debian installer

Bug#849400: debian-installer: LUKS on rootfs and boot

On Monday 26 December 2016 18:58:04 Cyril Brulebois wrote: > Hi, > > Pali Rohár (2016-12-26): > > Package: debian-installer > > Severity: normal > > > > Dear Maintainer, > > > > Debian installer refuse me to install entire system (including > > /boot) on > > > > one

Bug#849400: debian-installer: LUKS on rootfs and boot

Hi, Pali Rohár (2016-12-26): > Package: debian-installer > Severity: normal > > Dear Maintainer, > > Debian installer refuse me to install entire system (including /boot) on > one encrypted partition. It shows me this red fatal error message: > > [!!] Partition disks >

Bug#849400: debian-installer: LUKS on rootfs and boot

Package: debian-installer Severity: normal Dear Maintainer, Debian installer refuse me to install entire system (including /boot) on one encrypted partition. It shows me this red fatal error message: [!!] Partition disks Encryption configuration failure You have selected the root file