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 crypt_options: > - passphrase: zero terminated/no length parameter provided *shrug* > - passphrase_fd: pipe() to myself is prone to deadlock > - writing key material to a file: prone to missing cleanup and collisions > > Any way to get it done for a non-interactive program?
did you give cryptsetup 1.1.0 a try yet? its library api has many improvements compared to cryptsetup 1.0.6. it should be safe to upgrade to cryptsetup packages from debian/unstable within debian/lenny, as long as you don't ignore the instructions from NEWS.Debian. greetings, jonas
signature.asc
Description: Digital signature
