Okay, I'm forwarding this upstream and assigning to myself.
I think that there are two parts to this bug...
1) Key adding on underpowered cpu's (arms and atoms in netbooks) is
simply a slow process due to the 64K rounds of key strengthening. I
think we should make that configurable for Karmic, but there's nothing
we can really for this on Jaunty.
2) We should clean up the error messages thrown to the log files.
a) if the user doesn't have an ecryptfs setup, let's short circuit
pam_ecryptfs and bail out without spamming the logs with error messages
b) if the key is already in the keyring, great, no need to gripe about it.
:-Dustin
** Also affects: ecryptfs
Importance: Undecided
Status: New
** Changed in: ecryptfs
Importance: Undecided => Medium
** Changed in: ecryptfs
Status: New => Triaged
** Changed in: ecryptfs
Assignee: (unassigned) => Dustin Kirkland (kirkland)
** Changed in: ecryptfs-utils (Ubuntu)
Importance: Undecided => Medium
** Changed in: ecryptfs-utils (Ubuntu)
Status: New => Triaged
** Changed in: ecryptfs-utils (Ubuntu)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
--
Error attempting to add passphrase key to user session keyring
https://bugs.launchpad.net/bugs/313330
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
