From:
[email protected]
So, it turns out that there's more problems that creep up.
My mount also does a nice favour for me, and reorders the params such
that the options come AFTER the device and mount point, which breaks the parsing of options (such as the cipher type). Or, that's how it
appears...
My work around: change pam_mount.conf to directly call mount.crypt
instead of calling mount -t crypt. for cryptmount. As such, there's no
reason for me to put a symlink to mount.crypt in /sbin.
If I manage to rustle up some time, I look at fixing mount.crypt to be
more ordering-friendly, or at least spit out an error message when extra arguments are found. That being said, someone took a baseball bat to my
time machine, so my magic (patch generating) eightball says "future is
hazy. ask again later."
Cheers,
Vance Lankhaar
--
To UNSUBSCRIBE, email to
[email protected]
with a subject of "unsubscribe". Trouble? Contact
[email protected]
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)