Package: pmount
Severity: normal
The fix works for me, thanks a lot.
Regards,
Alex
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Vincent Fourmond wrote:
> > I grabbed the source and modified it slightly to print cryptsetup's console
> > output, which is shown below with pmount's debugging mode enabled:
> >
> > spawnv(): executing /sbin/cryptsetup '/sbin/cryptsetup' 'isLuks'
> > '/dev/sdb1'
> > spawn(): /sbin/cryptsetup t
Alexander Heinlein wrote:
> Vincent Fourmond wrote:
>>> The changelog of cryptsetup says:
>>> - new libcryptsetup API (documented in libcryptsetup.h)
>>>
>>> So it should not be too hard to adapt pmount to the new API.
>> Except that pmount does not use libcryptsetup, but only the cryptsetup
>> b
Vincent Fourmond wrote:
> > The changelog of cryptsetup says:
> > - new libcryptsetup API (documented in libcryptsetup.h)
> >
> > So it should not be too hard to adapt pmount to the new API.
>
> Except that pmount does not use libcryptsetup, but only the cryptsetup
> binary... So that does not
Alexander Heinlein wrote:
> Vincent Fourmond wrote:
>> Alexander Heinlein wrote:
>>> Same problem here. Downgrading cryptsetup from 1.1.0~rc2-1 back to 1.0.7-2
>>> solves the problem. But in contrast to the previous information, pmount
>>> prompts for a password here, but immediately after fails wi
Vincent Fourmond wrote:
> Alexander Heinlein wrote:
> > Same problem here. Downgrading cryptsetup from 1.1.0~rc2-1 back to 1.0.7-2
> > solves the problem. But in contrast to the previous information, pmount
> > prompts for a password here, but immediately after fails with
> > "Internal error: crypt
Package: pmount
Version: 0.9.20-2
Severity: normal
Hi.
Same problem here. Downgrading cryptsetup from 1.1.0~rc2-1 back to 1.0.7-2
solves the problem. But in contrast to the previous information, pmount
prompts for a password here, but immediately after fails with
"Internal error: cryptsetup luksO
7 matches
Mail list logo
