On 11/29/2011 05:44 PM, .. ink .. wrote: > > tested with cryptsetup version 1.4.1 > > When creating a cryptsetup mapper, cryptsetup will create two mappers > if the mapper name has characters in it that appear to be bash > special characters. Are the characters bash special characters or > cryptseup has its own set of characters that trigger this behavior? > > example, 1. Create a cryptsetup mapper with the following line: > cryptsetup luksOpen abc 'ab*c\d' Nice bug :) Seems that llibcryptsetup go through the failback (udev cannot create such name) and create own node. Add --debug and you will see the log. cryptsetup itself doesn't create device nodes and doesn't explicitly limit characted set. Anyway, I'll check and fix that somehow, maybe it is even fixed in lvm2 tree (where libdevmapper resides), thanks for reporting it. > I also noticed that these special characters are substituted by an > underscore character. The space character on the other hand just cuts > off the mapper name. This is an inconsistency and could be a bug. this is done by libdevmapper compare e.g. dmsetup create 'ab*c\d' --table "0 8 zero" For more info... (all device name issues apply to cryptsetup as well) https://bugzilla.redhat.com/show_bug.cgi?id=736486#c18 Milan _______________________________________________ dm-crypt mailing list dm-crypt@xxxxxxxx http://www.saout.de/mailman/listinfo/dm-crypt
