On 17/10/2007 David Härdeman wrote: > > Desc: check for UID == 0 before actually doing anything > > Author: Jonas Meurer <jonas@xxxxxxxxxxxxxxx> > > Date: 2007-08-14 > > URL: http://article.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt/2356 > > Patch: http://cache.gmane.org//gmane/linux/kernel/device-mapper/dm-crypt/2356-001.bin > > Debian: 03_check_for_root.dpatch > > This one we could probably change to just print an informative warning > message. We never know what kind of security a user has on his system now > or in the future (e.g. if someone starts implementing and using > capabilities, they might have the necessary permissions without being > root). I completely dropped that one. As Ludwig Nussel already mentioned, cryptsetup 1.0.5 seems to print meaningfull messages if permissions are wrong. > > Desc: run udevsettle after dm device creation > > Author: Matthias Koenig <mkoenig@xxxxxxxxxx> > > Date: 2007-06-20 > > URL: https://bugzilla.novell.com/show_bug.cgi?id=285478 > > Patch: https://bugzilla.novell.com/attachment.cgi?id=147410 > > This one is a workaround for a race in libdevmapper if I'm not mistaken. > While the debian package also carries the patch currently, I'm not sure it > should be fixed in cryptsetup (since other users of libdevmapper might > also be affected and libdevmapper needs to be fixed anyway). Ubuntu's > libdevmapper packages seems to have fixed this. Yes, sounds like a good plan. By the way, if ubuntu has a fix for libdevmapper, why is it not applied in debian? greetings, jonas --------------------------------------------------------------------- dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/ To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx For additional commands, e-mail: dm-crypt-help@xxxxxxxx
