I posted this now at http://code.google.com/p/cryptsetup/issues/detail?id=58
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
hey jan,
On 16/03/2010 Jan Engelhardt wrote:
> >did you give cryptsetup 1.1.0 a try yet? its library api has many
> >improvements compared to cryptsetup 1.0.6.
>
> Great, I'll try that. Thanks.
please report back whether your issues have been solved. i'll close the
bugreport in that case.
> >it
On 03/16/2010 06:13 PM, Jan Engelhardt wrote:
> Oh I'm not from Debian, I just remember that BTS is the cryptsetup
> anchorpoint ;)
well, upstream bug tracker is here http://code.google.com/p/cryptsetup/
But (as you see) Debian BTS works too :)
Please see the new libcryptsetup API (old calls al
On Tuesday 2010-03-16 13:37, Jonas Meurer wrote:
>
>hey jan,
>
>did you give cryptsetup 1.1.0 a try yet? its library api has many
>improvements compared to cryptsetup 1.0.6.
Great, I'll try that. Thanks.
>it should be safe to upgrade
>to cryptsetup packages from debian/unstable within debian/len
hey jan,
On 11/03/2010 Jan Engelhardt wrote:
> I was trying to change pam_mount to use libcryptsetup instead of forking
> out to /sbin/cryptsetup, but then I noticed I cannot pass in the binary
> key material via the library api. (There is no keyfile on disk, it's
> only in memory.)
>
> struct
5 matches
Mail list logo
