Bug in cryptsetup 2.3.0 (BitLocker key-file support)
Quentin Lefebvre <qlefebvre_pro-/[email protected]>
| Newsgroups | gmane.linux.kernel.device-mapper.dm-crypt |
|---|---|
| Message-ID | <[email protected]> |
Dear cryptsetup maintainer, I discovered a functional bug in the recently added BitLocker support (thanks by the way!) Not sure whether it is the place to report it... Summary: cryptsetup 2.3.0 cannot open a bitlk device when I provide a file containing its password (fails with error -2). Command failing: cryptsetup open --type bitlk --key-file <my_password_file> /dev/<bitlocker_device> bitlocker_mapping It is very easy to reproduce, so I don't copy paste the --debug output. I digged in the source code and found the problem in src/cryptsetup.c:543-545, where opt_keyfile_size is used when calling tools_get_key(). The workaround is actually to provide the exact password size on the command line, e.g.: cryptsetup open --type bitlk --keyfile-size 55 --key-file <my_recovery_password_file> /dev/<bitlocker_device> bitlocker_mapping Sorry not to provide a patch but I'm sure you will make it work in next releases. Hope this report helps a bit. Regards, Quentin _______________________________________________ dm-crypt mailing list [email protected] https://www.saout.de/mailman/listinfo/dm-crypt