EcryptFS development
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: ecryptfs@vger.kernel.org
Subject: ecryptfs doesn´t like noauto and noatime
Date: Mon, 16 Jan 2012 10:44:21 +0100	[thread overview]
Message-ID: <201201161044.21718.Martin@lichtvoll.de> (raw)

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.


Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

             reply	other threads:[~2012-01-16  9:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-16  9:44 Martin Steigerwald [this message]
2012-01-17  1:07 ` ecryptfs doesn´t like noauto and noatime Jakob Unterwurzacher
2012-01-17  8:37   ` Martin Steigerwald
2012-01-17  9:46     ` Jakob Unterwurzacher
2012-01-30 10:58       ` Martin Steigerwald
2012-01-30 18:49         ` Dustin Kirkland
2012-01-17  6:55 ` Tyler Hicks
2012-01-17  8:35   ` Martin Steigerwald

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201201161044.21718.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=ecryptfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox