Что я делаю не так когда пытаюсь получить доступ к линукс машине через ssh ключ?

Question

[Антон Мисягин]

ubuntu server 32bit 14.04
OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6, OpenSSL 1.0.1f 6 Jan 2014

Пробую с win 8.1 через putty
Мои действия.
ssh-keygen -t rsa
создались 2 файла id_rsa и id_rsa.pub
touch ~/.ssh/authorized_keys
cat id_rsa.pub >> authorized_keys
содержимое authorized_keys:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDTsN81f/yuwu38hzId93jZ/4KTCaIWXmt2NhviDn/CsEI6qA3viMCewsf0jklQ5ZCBrT6Rocpvk6wgGHqGjvZjWHPnponaUhBwgbSqrap/iz6Vog/P17IUXCAD7ULt78SPFvqCOc+BQfsIVL61/CBUTRDX4z1Qy5F5jjBk2EOJgYWID34V3GVvoQ9ziAg2m8KegHtjwG0FvYvOk8Bsmpl/ij2KpnXRaVkBrIZt4NgbjGD7UvYcrqxWRQH45o+sSM49pR85PmokgZ11SbpW3RA2cBwCvAHey2ZRTT6QuKM10X19+Yi5V0S1+1JfkaQsOgEOjd/XA4JxlaOqD5+Lr5sB deployer@server4e4o
копирую на винду id_rsa.
Открываю в puttygen. Load, Save private key. Сохраняю файл ppk. Открываю putty, указываю ip убунты, порт 22, пользователь deployer. SSH->Auth->Private key file. Открыть.
консоль пишет server refuzed our key. И просит пароль пользователя. Набираю - пускает.
Права на authorized_keys 600

Answer 1

[alegzz]

киньте конфиг ssh (/etc/ssh/sshd_config)

Comments

[Антон Мисягин]

# Package generated configuration file
# See the sshd_config(5) manpage for details

# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes

# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024

# Logging
SyslogFacility AUTH
LogLevel INFO

# Authentication:
LoginGraceTime 120
PermitRootLogin without-password
StrictModes yes

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile %h/.ssh/authorized_keys

# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes

# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no

# Change to no to disable tunnelled clear text passwords
#PasswordAuthentication yes

# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no

#MaxStartups 10:30:60
#Banner /etc/issue.net

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

Subsystem sftp /usr/lib/openssh/sftp-server

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

[Антон Мисягин]

строка AuthorizedKeysFile %h/.ssh/authorized_keys была закоментирована. Пробовал и так и так

[alegzz]

Антон Мисягин: это значение по-умолчанию. а команды "ssh-keygen -t rsa" и тп вы от чьего имени выполняете?

[Антон Мисягин]

deployer. Под которым потом пытаюсь зайти.

[Антон Мисягин]

2016-04-18 20:41:19 Looking up host "192.168.0.231"
2016-04-18 20:41:19 Connecting to 192.168.0.231 port 22
2016-04-18 20:41:19 We claim version: SSH-2.0-PuTTY_Release_0.66
2016-04-18 20:41:19 Server version: SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6
2016-04-18 20:41:19 We believe remote version has SSH-2 channel request bug
2016-04-18 20:41:19 Using SSH protocol version 2
2016-04-18 20:41:19 Doing Diffie-Hellman group exchange
2016-04-18 20:41:19 Doing Diffie-Hellman key exchange with hash SHA-256
2016-04-18 20:41:19 Host key fingerprint is:
2016-04-18 20:41:19 ssh-rsa 2048 51:d3:44:d1:e8:45:e5:ac:28:1d:cd:32:a1:70:74:3d
2016-04-18 20:41:19 Initialised AES-256 SDCTR client->server encryption
2016-04-18 20:41:19 Initialised HMAC-SHA-256 client->server MAC algorithm
2016-04-18 20:41:19 Initialised AES-256 SDCTR server->client encryption
2016-04-18 20:41:19 Initialised HMAC-SHA-256 server->client MAC algorithm
2016-04-18 20:41:19 Pageant is running. Requesting keys.
2016-04-18 20:41:19 Pageant has 1 SSH-2 keys
2016-04-18 20:41:19 Trying Pageant key #0
2016-04-18 20:41:19 Server refused our key

[Антон Мисягин]

но путти говорит что пальчики у нашего ключа такие: ssh-rsa 2048 fb:52:2b:c8:99:42:28:73:3d:19:6d:4c:ff:95:fb:2c

[Антон Мисягин]

какая-то нестыковка здесь

[Антон Мисягин]

А публичная часть ключа должна находиться только в authorized_keys файле, больше нигде?

[alegzz]

на сервере может в логах что?

[Антон Мисягин]

я в нем ничего не понимаю

[Антон Мисягин]

Apr 18 20:36:25 server4e4o sshd[1461]: Connection closed by 192.168.0.2 [preauth]
Apr 18 20:36:37 server4e4o sshd[1464]: Authentication refused: bad ownership or modes for directory /home/deployer
Apr 18 20:37:20 server4e4o sshd[1464]: pam_ecryptfs: pam_sm_authenticate: /home/deployer is already mounted
Apr 18 20:37:20 server4e4o sshd[1464]: Accepted password for deployer from 192.168.0.2 port 51931 ssh2
Apr 18 20:37:20 server4e4o sshd[1464]: pam_unix(sshd:session): session opened for user deployer by (uid=0)
Apr 18 20:37:20 server4e4o systemd-logind[412]: Removed session 2.
Apr 18 20:37:20 server4e4o systemd-logind[412]: New session 4 of user deployer.
Apr 18 20:37:40 server4e4o sudo: deployer : TTY=pts/0 ; PWD=/home/deployer ; USER=root ; COMMAND=/usr/bin/nano /etc/ssh/sshd_config
Apr 18 20:37:40 server4e4o sudo: pam_unix(sudo:session): session opened for user root by deployer(uid=0)
Apr 18 20:37:54 server4e4o sudo: pam_unix(sudo:session): session closed for user root
Apr 18 20:38:05 server4e4o sudo: deployer : TTY=pts/0 ; PWD=/home/deployer ; USER=root ; COMMAND=/usr/sbin/service ssh restart
Apr 18 20:38:05 server4e4o sudo: pam_unix(sudo:session): session opened for user root by deployer(uid=0)
Apr 18 20:38:05 server4e4o sshd[913]: Received signal 15; terminating.
Apr 18 20:38:06 server4e4o sshd[1601]: Server listening on 0.0.0.0 port 22.
Apr 18 20:38:06 server4e4o sshd[1601]: Server listening on :: port 22.
Apr 18 20:38:06 server4e4o sudo: pam_unix(sudo:session): session closed for user root
Apr 18 20:38:12 server4e4o sshd[1603]: Authentication refused: bad ownership or modes for directory /home/deployer
Apr 18 20:38:41 server4e4o sshd[1393]: pam_unix(sshd:session): session closed for user deployer
Apr 18 20:38:42 server4e4o sshd[1607]: Authentication refused: bad ownership or modes for directory /home/deployer
Apr 18 20:38:42 server4e4o sshd[1607]: pam_ecryptfs: pam_sm_authenticate: /home/deployer is already mounted
Apr 18 20:38:42 server4e4o sshd[1607]: Accepted password for deployer from 192.168.0.2 port 51963 ssh2
Apr 18 20:38:42 server4e4o sshd[1607]: pam_unix(sshd:session): session opened for user deployer by (uid=0)
Apr 18 20:38:42 server4e4o systemd-logind[412]: Removed session 3.
Apr 18 20:38:42 server4e4o systemd-logind[412]: New session 5 of user deployer.
Apr 18 20:39:00 server4e4o sshd[1658]: Authentication refused: bad ownership or modes for directory /home/deployer
Apr 18 20:39:00 server4e4o sshd[1658]: pam_ecryptfs: pam_sm_authenticate: /home/deployer is already mounted
Apr 18 20:39:00 server4e4o sshd[1658]: Accepted password for deployer from 192.168.0.2 port 51964 ssh2
Apr 18 20:39:00 server4e4o sshd[1658]: pam_unix(sshd:session): session opened for user deployer by (uid=0)
Apr 18 20:39:00 server4e4o systemd-logind[412]: New session 6 of user deployer.
Apr 18 20:40:02 server4e4o sshd[1658]: pam_unix(sshd:session): session closed for user deployer
Apr 18 20:40:13 server4e4o sshd[1711]: Connection closed by 192.168.0.2 [preauth]
Apr 18 20:41:18 server4e4o sshd[1715]: Authentication refused: bad ownership or modes for directory /home/deployer
Apr 18 20:50:13 server4e4o sshd[1726]: Connection closed by 192.168.0.2 [preauth]
Apr 18 20:52:20 server4e4o sshd[1731]: Authentication refused: bad ownership or modes for directory /home/deployer
Apr 18 20:52:20 server4e4o sshd[1731]: pam_ecryptfs: pam_sm_authenticate: /home/deployer is already mounted
Apr 18 20:52:20 server4e4o sshd[1731]: Accepted password for deployer from 192.168.0.2 port 52078 ssh2
Apr 18 20:52:20 server4e4o sshd[1731]: pam_unix(sshd:session): session opened for user deployer by (uid=0)
Apr 18 20:52:20 server4e4o systemd-logind[412]: Removed session 6.
Apr 18 20:52:20 server4e4o systemd-logind[412]: New session 7 of user deployer.

[Антон Мисягин]

Нашел здесь serverfault.com/questions/413231/how-to-get-all-fi... как из authorized_keys достать отпечатки. И получил, что на сервере такой же отпечаток как и дает pageant: 2048 fb:52:2b:c8:99:42:28:73:3d:19:6d:4c:ff:95:fb:2c imported-openssh-key (RSA)

[Антон Мисягин]

Откуда ssh-rsa 2048 51:d3:44:d1:e8:45:e5:ac:28:1d:cd:32:a1:70:74:3d в логе сессии putty? Может ssh сервер не оттуда берет ключи откуда я ожидаю. Как узнать какие отпечатки подходят к моему серверу?

[alegzz]

эм. а причем здесь отпечатки? отпечаток сервера находится в HostKey, этим ключом идентифицируется сам сервер (чтобы пользователь убедился, что он введет пароль не левому серверу). а отпечаток в публичном ключе, логично, совпадет с закрытым, тк открытый можно сгенерировать из закрытого
обратите внимание на строчку в логе о неверных правах. пробуйте так

chmod g-w /home/deployer 
chmod 700 /home/deployer/.ssh
chmod 600 /home/deployer/.ssh/authorized_keys

[Антон Мисягин]

chmod g-w /home/deployer помогла!!! зашел

[alegzz]

эм. отметье ответ как решение

[Антон Мисягин]

Спасибо)

Answer 2

[Антон Мисягин]

Если через pageant делать, то консоль даже не пишет, что ключ отвергнут, а сразу предлагает ввести пароль пользователя