On Mon, October 15, 2007 19:06, Jonas Meurer wrote: > I maintain a list of patches for cryptsetup which have not been accepted > and applied upstream yet, to keep track of them for debians package > maintainance. Since I have write access to the repo, and Clemens seem to be quite busy these days, I could try to find time this weekend to review and apply the patches (unless someone objects). Comments on two of the patches below. > 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). > 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. -- David Härdeman --------------------------------------------------------------------- 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
