Bug#353755: [Pkg-cryptsetup-devel] Bug#353755: cryptsetup: luksOpen
on read only device without --readonly fails silently
jonas at freesources.org
Mon Feb 20 20:55:20 UTC 2006
On 20/02/2006 Bastian Kleineidam wrote:
> the command "cryptsetup luksOpen /dev/hdc" does not work here. The
> /dev/mapper/_image device is not created, but the exit code is still
> zero. The /dev/hdc is my DVD-ROM device with a burned LUKS image.
> The strace output reveals that this call fails:
> ioctl(3, DM_TABLE_LOAD, 0x809cd80) = -1 EINVAL (Invalid argument)
> However it works when I add the "--readonly" option:
> ioctl(3, DM_TABLE_LOAD, 0x809cda0) = 0
> The strace outputs for both cases are attached, with private data
> (password and image data) removed.
> I expected the command without --readonly to not fail silently, but
> to print an error message and exit with a non-zero status.
i guess that this is the same upstream bug as reported in #258376
even if it's not about the same particular action, it's the same general
problem, that cryptsetup prints missleading messages, and even fails
(exitcode 1) with error-messages in cases where it should only print a
can you verify this? if yes, the bugs could be merged.
More information about the Pkg-cryptsetup-devel