sshd get path to authorized_keys file wrong
Barry Scott
barry.scott at onelan.co.uk
Thu Jun 10 10:45:18 UTC 2010
We are seeing an sshd_config that used to work on f12 failing on f13.
When doing ssh root at host:
Jun 10 11:34:32 f12barry sshd[23030]: debug1: temporarily_use_uid: 0/0 (e=0/0)
Jun 10 11:34:32 f12barry sshd[23030]: debug1: trying public key file //.ssh/authorized_keys
Jun 10 11:34:32 f12barry sshd[23030]: debug1: restore_uid: 0/0
Jun 10 11:34:32 f12barry sshd[23030]: debug1: temporarily_use_uid: 0/0 (e=0/0)
Jun 10 11:34:32 f12barry sshd[23030]: debug1: trying public key file //.ssh/authorized_keys
Jun 10 11:34:32 f12barry sshd[23030]: debug1: restore_uid: 0/0
Jun 10 11:34:32 f12barry sshd[23030]: Failed publickey for root from 192.168.7.232 port 39169 ssh2
Notice the public key file is //.ssh/authorized_keys.
The sshd_config we use is:
-------------------sshd_config--------------
Port 22
Protocol 2
SyslogFacility AUTHPRIV
LogLevel DEBUG3
MaxStartups 2
PermitRootLogin yes
UsePAM yes
GatewayPorts no
AuthorizedKeysFile .ssh/authorized_keys
# We renable later for root only
PubkeyAuthentication no
AllowTcpForwarding no
X11Forwarding no
AllowUsers root
ChallengeResponseAuthentication no
# 60 second server-side timeout
ClientAliveCountMax 3
ClientAliveInterval 20
Match User root
X11Forwarding yes
AllowTcpForwarding yes
PubkeyAuthentication yes
-------------------sshd_config--------------
Changing AuthorizedKeysFile value has no effect on the path check in the debug log.
Has sshd got a bug in it or is there more config files that need to be changed
to allow the authorized_keys to be found?
Barry
Barry
More information about the users
mailing list