Earlier this week, I uploaded ecryptfs-utils-78 to karmic, which
should address the issue you mention.
The fix first detects if your encrypted home or private directory is
already mounted, and if so, it bypasses the most performance intensive
work.
This means that all subsequent authentications t
** Changed in: ecryptfs-utils (Ubuntu)
Status: Confirmed => Fix Released
--
pam_encryptfs.so causes authentication to be slow
https://bugs.launchpad.net/bugs/295429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Changed in: ecryptfs-utils (Ubuntu)
Importance: Undecided => Medium
** Changed in: ecryptfs-utils (Ubuntu)
Status: Incomplete => Confirmed
--
pam_encryptfs.so causes authentication to be slow
https://bugs.launchpad.net/bugs/295429
You received this bug notification because you are a
Please fix it!
Sometimes, after standby my machine needs more than 10 sec. to unlock the
gnome-screensaver. This is ridiculous.
As said before, the key is already there the ecryptfs is already mounted. No
need to unwrap the passphrase at unlock-time.
Thank you!
--
pam_encryptfs.so causes authen
This would be nice. It still annoys me that it takes longer for sudo to
work when I get the password right than when I get it wrong, even though
the encrypted directory is already unlocked (and so it seems to me that
all of that time is completely wasted: the key is never going to be
used)
--
pam
OK, my proposal was missing something - you need the password to
unwrap... :-p
So the best would IMHO that you simply check that the password is the right one
during the auth phase, and only unwrap the folder after, for example in a child
process. For now, in the pam_sm_authenticate function, th
Dustin: Have you considered moving unwrap to PAM session phase, instead
of auth? It makes no sense to me to block the whole authentication to
mount your encrypted folder. The auth phase should be reserved to
authentication checking - session is here for you, where you can do this
while starting oth
Hi all,
Thanks for the bug report.
Okay I've tracked this down. It helped quite a bit to see that it's
mostly Atom processors (eee pc's, and netbooks).
This is totally a function of eCryptfs' key strengthening mechanism. For more
information about key strengthening, see:
* http://en.wikipedi
Hi, same "problem" here, eee 701 with ecryptfs:
slow login (~5sec) and same delay on every other operation that involve
authentication... as sudo.
As described by Dustin, i think problem is cpu related; to test try the
following:
open 2 terminal (shell)
in the first type "top -d1" to show cpu us
I notice it mostly on my eee 701, where it will timeout when I get it
wrong faster than it will go through when I get it right. This is
something like 800Mhz with 2Gb RAM. However, my dev laptop is dual core,
1.66Ghz per core, and it's a noticeable (although less) delay there
also.
I don't know an
On Mon, 2009-01-26 at 05:27 +, Dustin Kirkland wrote:
> How much CPU/Memory do you have on the slow systems?
I'm using a Dell Mini 12, which is a dual-core
Intel(R) Atom(TM) CPU Z530 @ 1.60GHz (which often
throttles down to 800MHz), with 1 GB RAM. I
was seeing something that was taking a ve
How much CPU/Memory do you have on the slow systems?
In a rather minimal virtual machine (fraction of a processor, 256MB
memory), the login process can take up to 2 seconds. I'd say maybe 2
seconds might be expected. 4 or 5 seconds seems rather long on normal
hardware...
A few nitty gritty deta
'k, attaching common-password.
** Attachment added: "common-password"
http://launchpadlibrarian.net/19920086/common-password
--
pam_encryptfs.so causes authentication to be slow
https://bugs.launchpad.net/bugs/295429
You received this bug notification because you are a member of Ubuntu
Bugs,
On Mon, Nov 24, 2008 at 7:15 PM, Dustin Kirkland
<[EMAIL PROTECTED]> wrote:
> The only difference between your config and mine is:
Sorry to leave you hanging ... I have samba line in mine.
--
:-Dustin
--
pam_encryptfs.so causes authentication to be slow
https://bugs.launchpad.net/bugs/295429
Sorry, I mean common-password, not login.
The only difference between your config and mine is:
:-Dustin
--
pam_encryptfs.so causes authentication to be slow
https://bugs.launchpad.net/bugs/295429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Attached. I didn't have common-login, but I did have login, which I've
included instead.
I see this on two computers, one is a fresh Intrepid install, one an
upgrade.
** Attachment added: "pam-common.tar.gz"
http://launchpadlibrarian.net/19918416/pam-common.tar.gz
--
pam_encryptfs.so causes
Could you guys post your:
* /etc/pam.d/common-auth
* /etc/pam.d/common-login
* /etc/pam.d/common-session
files?
There might be something else odd going on in there ...
:-Dustin
--
pam_encryptfs.so causes authentication to be slow
https://bugs.launchpad.net/bugs/295429
You received this bug
This also happens to me. Similar logs to the ones shown above. Similar
5 second pause.
My PC was upgraded to hardy and I used the following URL to setup the
Private directory: https://wiki.ubuntu.com/EncryptedPrivateDirectory
--
pam_encryptfs.so causes authentication to be slow
https://bugs.la
18 matches
Mail list logo
