Jonas Meurer <[EMAIL PROTECTED]> wrote:
> > However, we fixed the bug. The problem was that I restricted the length
> > (number of sectors) of a temporary dm-crypt mapping. However for devices
> > with non-512 sector size like DVDs, the length as well as the start must
> > be aligned to (device_se
On 12/03/2006 Clemens Fruhwirth wrote:
> Execuse me for being not highly "verbose" on this issue. I mailed
> Bastian in private a tarball with a fix. I haven't Cc'ed
> bugs.debian.org as I was not sure whether the bug tracking system
> handles attachments correctly. (Does it?)
yes, the but trackin
Jonas Meurer <[EMAIL PROTECTED]> wrote:
> i've tried to reproduce this bug, and indeed luksOpen fails for me with
> a similar error message. i tried also plain dm-crypt, and discovered
> that 'cryptsetup create' doesn't fail. the created device is mountable
> and contains all the data which i put
On 09/03/2006 Bastian Kleineidam wrote:
> You wrote:
> > Do you have the image still on disk? Can you try to open it via the
> > loopback driver?
> >
> > losetup /dev/loopX image
> > cryptsetup --readonly /dev/loopX _image
>
> The losetup case works. Everything I do on disk works fine, only on DVD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
You wrote:
> Do you have the image still on disk? Can you try to open it via the
> loopback driver?
>
> losetup /dev/loopX image
> cryptsetup --readonly /dev/loopX _image
>
> Does this fail?
The losetup case works. Everything I do on disk works fi
Jonas Meurer <[EMAIL PROTECTED]> wrote:
> after upgrading cryptsetup I was not able to use luksOpen on a
> DVD image file. Downgrading to 2:1.0.1-16 makes it work again,
> so something in the upgrade broke things.
> Here is the command line log with the old 1.0.1 version:
> $ cryptsetup --readonly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jonas,
Jonas Meurer schrieb:
> could you try whether the --readonly flag works for normal encrypted
> filesystems on a harddisk? for me it works.
Mounting normal encrypted filesystems works. Mounting them with
- --readonly works also. What I cannot
On 03/03/2006 Bastian Kleineidam wrote:
> after upgrading cryptsetup I was not able to use luksOpen on a
> DVD image file. Downgrading to 2:1.0.1-16 makes it work again,
> so something in the upgrade broke things.
> Here is the command line log with the old 1.0.1 version:
> $ cryptsetup --readonly
Package: cryptsetup
Version: 2:1.0.2+1.0.3-rc2-1
Severity: grave
Justification: causes non-serious data loss
Hi,
after upgrading cryptsetup I was not able to use luksOpen on a
DVD image file. Downgrading to 2:1.0.1-16 makes it work again,
so something in the upgrade broke things.
Here is the comm
9 matches
Mail list logo
