Bug#697905: persistent naming in crypttab

2015-02-15 Thread Trek
as I have installed jessie with debootstrap, I cannot verify if the swap config lines in /etc/crypttab are safe now, but reading the source they are not the patch I proposed 2 years ago sadly run only on linux but not on kfreebsd nor hurd may be that in the meanwhile we can add a warning in the R

Bug#697905: persistent naming in crypttab

2013-02-03 Thread Ben Hutchings
On Sun, 2013-02-03 at 21:53 +0100, Cyril Brulebois wrote: > Hi, > > Trek (11/01/2013): > > I have attached an untested patch to partman-crypto that should address > > this issue. As this is my first look of debian installer sources, this > > patch is not intended to be applied as is, but as a det

Bug#697905: persistent naming in crypttab

2013-02-03 Thread Cyril Brulebois
Hi, Trek (11/01/2013): > I have attached an untested patch to partman-crypto that should address > this issue. As this is my first look of debian installer sources, this > patch is not intended to be applied as is, but as a detailed > explanation of the fix. The /etc/crypttab would be: > > sda1_

Bug#697905: persistent naming in crypttab

2013-01-11 Thread Ropesh Thouna
Please unsubscribe.. Thank you. On Fri, Jan 11, 2013 at 2:49 PM, Trek wrote: > Package: partman-crypto > Version: 56 > > Hi, > > I think that using udev persistent device naming in /etc/crypttab > would be useful to prevent some dangerous situation, like the > following one. > > I have a 3 disk

Bug#697905: persistent naming in crypttab

2013-01-11 Thread Trek
Package: partman-crypto Version: 56 Hi, I think that using udev persistent device naming in /etc/crypttab would be useful to prevent some dangerous situation, like the following one. I have a 3 disks setup with the first two in raid mode and the third as archive. The swap partitions are encrypte