On 16.01.2012 10:44, Martin Steigerwald wrote: > Hi! > > I have > > merkaba:~> grep ecrypt /etc/fstab > /home/.ms /home/ms ecryptfs > noatime,noauto 0 0 > > And get: > > merkaba:~> mount /home/ms > Passphrase: > Attempting to mount with the following options: > ecryptfs_unlink_sigs > ecryptfs_fnek_sig=0408d19ec184c207 > ecryptfs_key_bytes=32 > ecryptfs_cipher=aes > ecryptfs_sig=0408d19ec184c207 > Error mounting eCryptfs: [-5] Input/output error > Check your system logs; visit <http://launchpad.net/ecryptfs> > > > Still it works. > > > In dmesg I see: > > [ 2657.888355] ecryptfs_parse_options: eCryptfs: unrecognized option > [noauto] > [ 2657.888359] ecryptfs_parse_options: eCryptfs: unrecognized option > [noatime] > [ 2657.913215] alg: No test for __gcm-aes-aesni (__driver-gcm-aes-aesni) > > > Thus I removed at least noatime, but then I still see: > > [ 2839.460200] ecryptfs_parse_options: eCryptfs: unrecognized option > [noauto] > > > On could argue about noatime when ecryptfs doesn´t override the setting of > the underlying filesystem - i.e. doesn´t write the atime itself. But I > think noauto should be silently ignored. > > Without noatime it would ask me the passwort upon boot, but I do not like > that since I do not use that user everytime. > > I could use mounting via pam, but I like to have a different password for > the user stored in /etc/shadow than the password from the filesystem > itself. Note that this should work by creating ~/.ecryptfs/wrapping-independent . Pam will ask for the ecryptfs password explicetely then. Jakob -- To unsubscribe from this list: send the line "unsubscribe ecryptfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
