Public key ssh auth doesn't work in Jaunty
Spent all night to understand why public key ssh auth doesn't work. It seems to me that issue only affects Jaunty. Please have a look at the details below.
So, the configuration is:
1. Client
- lsb_release: Ubuntu 8.10 intrepid
- ssh-client: OpenSSH_5.1p1 Debian-3ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
2. Server A
- lsb_release: Ubuntu 8.04.2 hardy
- sshd: OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007
3. Server B
- lsb_release: Ubuntu 9.04 jaunty
- sshd: OpenSSH_5.1p1 Debian-5ubuntu1, OpenSSL 0.9.8g 19 Oct 2007
Server A and Server B have the same /etc/ssh/
RSAAuthentication yes
PubkeyAuthentic
StrictModes no
I turned StrictModes to "no", but every server has the same permissions on user's .ssh folder and .ssh/authorized
So, I am able to connect with public key from Client machine to Server A, but I can't connect to Server B.
I run ssh client and sshd on Server B in debug mode, please find logs attached.
Most important strings from auth.log:
...
Apr 16 20:58:47 ubuntu sshd[21728]: debug3: mm_request_receive entering
Apr 16 20:58:47 ubuntu sshd[21728]: debug3: monitor_read: checking request 21
Apr 16 20:58:47 ubuntu sshd[21728]: debug3: mm_answer_
Apr 16 20:58:47 ubuntu sshd[21728]: debug3: mm_answer_
Apr 16 20:58:47 ubuntu sshd[21728]: debug1: Checking blacklist file /usr/share/
Apr 16 20:58:47 ubuntu sshd[21728]: debug1: Checking blacklist file /etc/ssh/
Apr 16 20:58:47 ubuntu sshd[21728]: debug1: temporarily_
Apr 16 20:58:47 ubuntu sshd[21728]: debug1: trying public key file /home/sasha/
Apr 16 20:58:47 ubuntu sshd[21728]: debug1: restore_uid: 0/0
Apr 16 20:58:47 ubuntu sshd[21728]: debug1: temporarily_
Apr 16 20:58:47 ubuntu sshd[21728]: debug1: trying public key file /home/sasha/
Apr 16 20:58:47 ubuntu sshd[21728]: debug1: restore_uid: 0/0
Apr 16 20:58:47 ubuntu sshd[21728]: Failed publickey for sasha from 10.0.0.11 port 51194 ssh2
Apr 16 20:58:47 ubuntu sshd[21728]: debug3: mm_answer_
...
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- eCryptfs Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- sasha
- Solved:
- Last query:
- Last reply:
This question was originally filed as bug #362427.