Comment 6 for bug 313330

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