Can't login via ssh with public key because of encryptfs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I'm running on development version of Jaunty.
It seems that I can't login via ssh with public key because of encryptfs.
ssh -v -p 1022 10.0.0.1 shows:
...
debug1: SSH2_MSG_
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering public key: /home/sasha/
debug1: Authentications that can continue: publickey,password
debug1: Offering public key: id_dsa
debug1: Authentications that can continue: publickey,password
debug1: Offering public key: id_dsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /home/sasha/
debug1: Trying private key: /home/sasha/
debug1: Next authentication method: password
cat /var/log/auth.log | grep ssh shows:
Apr 16 00:53:58 ubuntu sshd[31597]: pam_sm_
Apr 16 00:53:58 ubuntu sshd[31597]: pam_sm_
Apr 16 00:53:58 ubuntu sshd[31597]: Warning: Using default salt value (undefined in ~/.ecryptfsrc)
Apr 16 00:54:02 ubuntu sshd[31617]: Passphrase key already in keyring; rc = [1]
Apr 16 00:54:02 ubuntu sshd[31617]: ecryptfs_
Apr 16 00:54:02 ubuntu sshd[31617]: Error attempting to add filename encryption key to user session keyring; rc = [1]
Apr 16 00:54:03 ubuntu sshd[31617]: Passphrase key already in keyring; rc = [1]
Apr 16 00:54:03 ubuntu sshd[31617]: ecryptfs_
Apr 16 00:54:03 ubuntu sshd[31617]: Error attempting to add passphrase key to user session keyring; rc = [1]
Apr 16 00:54:03 ubuntu sshd[31617]: There is already a key in the user session keyring for the given passphrase.
Apr 16 00:54:03 ubuntu sshd[31597]: Accepted password for sasha from 10.0.0.11 port 58989 ssh2
Apr 16 00:54:03 ubuntu sshd[31597]: pam_unix(
Apr 16 00:54:03 ubuntu sshd[31597]: Mount of private directory return code [0]
It seems that I'am wrong. Please close this bug, I guess the issue is not related to encryptfs. LogLevel of sshd shows me more details on the issue.