Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping (fwd)
reopen 768314 reassign 768314 systemd tags 768314 + help thanks It would be very nice, if concerned people could test systemd from experimental with a cryptsetup, so the patches could be maybe backported into jessie. (reopening since this bug is closed and reassigning to systemd, since that's currently the scope within which this problem could be solved IMHO) *t On Wed, 7 Jan 2015, Tomas Pospisek wrote: Thanks Zbigniew Kjetil and Christian is it possible for you to test this? *t On Wed, 7 Jan 2015, Zbigniew Jędrzejewski-Szmek wrote: On Tue, Jan 06, 2015 at 06:56:11PM +0100, Tomas Pospisek wrote: Hello Zbigniew, I was told on IRC in #debian-systemd: mbiebl_ tpo, I remember Zbigniew had a patch without wanting to stress anybody: could you maybe tell me what the status of that patch is? Are you considering it ready for inclusion in Debian's systemd? Is it possible that it would be ready and included prior to jessie's release? systemd git should now avoid output when waiting for the password. IIRC, my initial patch was followed up by a few cleanups, so it might not be very backportable, but latest systemd in experimental should have all the changes. I'd suggest that you test if that version works for you. Zbyszek
Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping (fwd)
Hello Kjetil, On Wed, 7 Jan 2015, Kjetil Kjernsmo wrote: On Wednesday 7. January 2015 08.23.32 Tomas Pospisek wrote: Kjetil and Christian is it possible for you to test this? As of now, I only have my laptop to test Jessie, which is something I use every day, and so I'm anxious about putting such an important thing as systemd from experimental on it. I've had the ambition to be able to easily set up virtual hosts for these occasions for a long time, but alas, ENOTIME. well, this is quite demotivating. I am not concerned by the cryptosetup problem, I just wanted to help make the upgrade to the coming release better for people that are using crypted partitions. But lets see, whether you're maybe able to contribute just a tiny bit - Other than dropping the effort to try to improve on this particular problem I see two ways forward: a) you could test on your computer and I help you a bit b) I could test on my computer and you help me a bit ab=c) we could both test Let's see a) You can do: # apt-get install lxc # lxc-create -n test_VM -t debian -- -r jessie This will create a VM under /var/lib/lxc/test_VM, that you can easilly remove later with # rm -r /var/lib/lxc/test_VM You can start the VM with: # lxc-start -n test_VM If you go and do something different while lxc-create is downloading its stuff, the whole thing takes about 1 minute of your time. After that you can set up the crypted device and install systemd from experimental inside and see whether it works. Now way forward b) == Could you tell me how to quickly set up a crypt device? Please let me know what you think, greetings, *t -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping (fwd)
On Wednesday 7. January 2015 08.23.32 Tomas Pospisek wrote: Kjetil and Christian is it possible for you to test this? As of now, I only have my laptop to test Jessie, which is something I use every day, and so I'm anxious about putting such an important thing as systemd from experimental on it. I've had the ambition to be able to easily set up virtual hosts for these occasions for a long time, but alas, ENOTIME. Cheers, Kjetil
Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping (fwd)
On Tue, Jan 06, 2015 at 06:56:11PM +0100, Tomas Pospisek wrote: Hello Zbigniew, I was told on IRC in #debian-systemd: mbiebl_ tpo, I remember Zbigniew had a patch without wanting to stress anybody: could you maybe tell me what the status of that patch is? Are you considering it ready for inclusion in Debian's systemd? Is it possible that it would be ready and included prior to jessie's release? systemd git should now avoid output when waiting for the password. IIRC, my initial patch was followed up by a few cleanups, so it might not be very backportable, but latest systemd in experimental should have all the changes. I'd suggest that you test if that version works for you. Zbyszek -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping (fwd)
Thanks Zbigniew Kjetil and Christian is it possible for you to test this? *t On Wed, 7 Jan 2015, Zbigniew Jędrzejewski-Szmek wrote: On Tue, Jan 06, 2015 at 06:56:11PM +0100, Tomas Pospisek wrote: Hello Zbigniew, I was told on IRC in #debian-systemd: mbiebl_ tpo, I remember Zbigniew had a patch without wanting to stress anybody: could you maybe tell me what the status of that patch is? Are you considering it ready for inclusion in Debian's systemd? Is it possible that it would be ready and included prior to jessie's release? systemd git should now avoid output when waiting for the password. IIRC, my initial patch was followed up by a few cleanups, so it might not be very backportable, but latest systemd in experimental should have all the changes. I'd suggest that you test if that version works for you. Zbyszek
Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping (fwd)
Hello Zbigniew, I was told on IRC in #debian-systemd: mbiebl_ tpo, I remember Zbigniew had a patch without wanting to stress anybody: could you maybe tell me what the status of that patch is? Are you considering it ready for inclusion in Debian's systemd? Is it possible that it would be ready and included prior to jessie's release? *t On Sat, 3 Jan 2015, Tomas Pospisek wrote: Hello systemd maintainers Laurent, bug #768314 [0] has been reassigned to the release-notes. It's about a user not being able to enter his cryptsetup password. A solution seems to be to install plymouth. It seems, that's a known problem, as noted in your titanpad [1]. However I could not find a respective issue in the BTS entries for systemd [2] - is there one that tracks this problem? Do you have any idea how this problem should be resolved for jessie? The original owner of the bug report suggests raising plymouth to a Recommends dependency. I suggested that systemd could recognize that there are mounted crypted partitions and suggest to the user to install plymouth at postinst time. Another workaround would be to just document the problem in the release notes and hope users won't run into it. Do you see or prefer any other approach? Second question: in the titanpad entry you write The plan with plymouth 0.9.0-9 is to not require any modification to the kernel cmdline and enable the I/O multiplexing functionality by default when the pkg is installed. As far as I can see from the plymouth changelog [3] no solution was implemented for this problem [4] in 0.9.0-9 and there hasn't been any activity in that bug report since Nov 14th. What's the current goal/aim wrt that bug? Thanks, *t [0] https://bugs.debian.org/768314 [1] https://debian.titanpad.com/23? [2] http://bugs.debian.org/systemd [3] http://metadata.ftp-master.debian.org/changelogs//main/p/plymouth/plymouth_0.9.0-9_changelog [4] https://bugs.debian.org/768329 @bugs.debian.org -- Forwarded message -- Date: Tue, 30 Dec 2014 23:11:58 +0100 From: Jonas Meurer jo...@freesources.org To: Tomas Pospisek t...@sourcepole.ch, 768...@bugs.debian.org Cc: Kjetil Kjernsmo kje...@kjernsmo.net Subject: Re: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping Hi Tomas, thanks for taking care of the bugreport. Am 30.12.2014 um 19:27 schrieb Tomas Pospisek: Hello Jonas Kjetil, (context: I'm reading through release-notes bug reports). I'm not sure I understand what you are expecting as a result by cloning/reassigning this to the release notes - Let me try to understand the problem: * if there's an encrypted partition, then systemd, who aparently would be responsible to do so will not prompt for the password, if plymouth is not installed. Is my understanding of the problem correct? Yes. Actually, it is even more complicated, but your understanding is correct: Systemd includes its own dm-crypt/cryptsetup device unlocking functions. With systemd as init system, it processes all dm-crypt encrypted devices that shall be unlocked during the boot process and *after* initramfs. I don't know systemd, but from the bugreports I learned that it apparently doesn't implement a proper mechanism to prompt for user input itself. Instead it relies on plymouth doing that task. As a result, systemd without plymouth doesn't wait for user input at unlocking dm-crypt devices but instead continues to print boot logging output to the console. So I think the right thing to do would be, that during the upgrade the systemd postinstallation should check whether there are some mounted partitions that are crypted and then recommend to install plymouth. Do you concur? I would even go futher and say that systemd should recommend plymouth in any case. Still, if it's only recommended and not a hard dependency, the discovered behaviour should be documented in the release notes in my eyes. Otherwise, should the release-notes recommend to install plymouth to the user if s/he has crypted partitions that should get mounted during boot? Yes, that's what needs to be done at least. Ideally IMHO the release notes should also explain the problem in sufficient technical detail to allow the user to take his own steps to further understand the problem and to choose an alternative solution if he deems so. Optimally you could suggest a wording? Unfortunately I've not enough knowledge about systemd to propose a wording. But feel free to use anything I wrote in the bugreport for a draft. Cheers, jonas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768314: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping (fwd)
Hello systemd maintainers Laurent, bug #768314 [0] has been reassigned to the release-notes. It's about a user not being able to enter his cryptsetup password. A solution seems to be to install plymouth. It seems, that's a known problem, as noted in your titanpad [1]. However I could not find a respective issue in the BTS entries for systemd [2] - is there one that tracks this problem? Do you have any idea how this problem should be resolved for jessie? The original owner of the bug report suggests raising plymouth to a Recommends dependency. I suggested that systemd could recognize that there are mounted crypted partitions and suggest to the user to install plymouth at postinst time. Another workaround would be to just document the problem in the release notes and hope users won't run into it. Do you see or prefer any other approach? Second question: in the titanpad entry you write The plan with plymouth 0.9.0-9 is to not require any modification to the kernel cmdline and enable the I/O multiplexing functionality by default when the pkg is installed. As far as I can see from the plymouth changelog [3] no solution was implemented for this problem [4] in 0.9.0-9 and there hasn't been any activity in that bug report since Nov 14th. What's the current goal/aim wrt that bug? Thanks, *t [0] https://bugs.debian.org/768314 [1] https://debian.titanpad.com/23? [2] http://bugs.debian.org/systemd [3] http://metadata.ftp-master.debian.org/changelogs//main/p/plymouth/plymouth_0.9.0-9_changelog [4] https://bugs.debian.org/768329 @bugs.debian.org -- Forwarded message -- Date: Tue, 30 Dec 2014 23:11:58 +0100 From: Jonas Meurer jo...@freesources.org To: Tomas Pospisek t...@sourcepole.ch, 768...@bugs.debian.org Cc: Kjetil Kjernsmo kje...@kjernsmo.net Subject: Re: [pkg-cryptsetup-devel] Bug#768314: cryptsetup: Passphrase prompt rolls by without stopping Hi Tomas, thanks for taking care of the bugreport. Am 30.12.2014 um 19:27 schrieb Tomas Pospisek: Hello Jonas Kjetil, (context: I'm reading through release-notes bug reports). I'm not sure I understand what you are expecting as a result by cloning/reassigning this to the release notes - Let me try to understand the problem: * if there's an encrypted partition, then systemd, who aparently would be responsible to do so will not prompt for the password, if plymouth is not installed. Is my understanding of the problem correct? Yes. Actually, it is even more complicated, but your understanding is correct: Systemd includes its own dm-crypt/cryptsetup device unlocking functions. With systemd as init system, it processes all dm-crypt encrypted devices that shall be unlocked during the boot process and *after* initramfs. I don't know systemd, but from the bugreports I learned that it apparently doesn't implement a proper mechanism to prompt for user input itself. Instead it relies on plymouth doing that task. As a result, systemd without plymouth doesn't wait for user input at unlocking dm-crypt devices but instead continues to print boot logging output to the console. So I think the right thing to do would be, that during the upgrade the systemd postinstallation should check whether there are some mounted partitions that are crypted and then recommend to install plymouth. Do you concur? I would even go futher and say that systemd should recommend plymouth in any case. Still, if it's only recommended and not a hard dependency, the discovered behaviour should be documented in the release notes in my eyes. Otherwise, should the release-notes recommend to install plymouth to the user if s/he has crypted partitions that should get mounted during boot? Yes, that's what needs to be done at least. Ideally IMHO the release notes should also explain the problem in sufficient technical detail to allow the user to take his own steps to further understand the problem and to choose an alternative solution if he deems so. Optimally you could suggest a wording? Unfortunately I've not enough knowledge about systemd to propose a wording. But feel free to use anything I wrote in the bugreport for a draft. Cheers, jonas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
