☰

공개 키를 사용하여 SSH를 통해 서버에 연결

tag-icon • tag-icon debian ssh key-authentication
공개 키를 사용하여 SSH를 통해 서버에 연결

(내 앞에이런 질문을 했어요그러나 OSX를 실행하는 MacBook에서 키가 제대로 작동하는지 테스트한 후 문제는 Debian에 있는 것 같습니다.)

질문

최근 데비안 머신을 설정했는데(데비안 사용 경험이 많지 않음) SSH를 사용하여 서버(192.168.1.31)에 제대로 연결할 수 없는 것 같습니다.

초기 구성 후 서버가 내 키를 수락하는 것 같지만 서명 확인에 실패합니다.

초기 구성은 제가 항상 하는 작업입니다.

  1. 생성키()ssh-keygen -t rsa -b 4096 -C "[email protected]"
  2. 그걸로 추가해ssh-add
  3. SSH 서버에 공개키 등록

데비안 클라이언트ssh [email protected] -vvv

OpenSSH_7.4p1 Debian-10+deb9u2, OpenSSL 1.0.2l  25 May 2017
debug1: Reading configuration data /home/daniel/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "192.168.1.31" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 192.168.1.31 [192.168.1.31] port 22.
debug1: Connection established.
debug1: identity file /home/daniel/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/daniel/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/daniel/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/daniel/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/daniel/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/daniel/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/daniel/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/daniel/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.4p1 Debian-10+deb9u2
debug1: Remote protocol version 2.0, remote software version 7.15 FlowSsh: Bitvise SSH Server (WinSSHD) 7.15
debug1: no match: 7.15 FlowSsh: Bitvise SSH Server (WinSSHD) 7.15
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 192.168.1.31:22 as 'dn'
debug3: hostkeys_foreach: reading file "/home/daniel/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/daniel/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from 192.168.1.31
debug3: order_hostkeyalgs: prefer hostkeyalgs: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521
debug3: send packet: type 20
debug1: SSH2_MSG_KEXINIT sent
debug3: receive packet: type 20
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256,[email protected],ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: [email protected],[email protected],[email protected],ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc
debug2: ciphers stoc: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc
debug2: MACs ctos: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,[email protected],zlib
debug2: compression stoc: none,[email protected],zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: ecdh-sha2-1.3.132.0.10,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,ext-info-s
debug2: host key algorithms: rsa-sha2-512,rsa-sha2-256,ssh-rsa,ecdsa-sha2-nistp384
debug2: ciphers ctos: [email protected],[email protected],aes256-ctr,aes192-ctr,aes128-ctr,3des-ctr
debug2: ciphers stoc: [email protected],[email protected],aes256-ctr,aes192-ctr,aes128-ctr,3des-ctr
debug2: MACs ctos: hmac-sha2-256,hmac-sha1
debug2: MACs stoc: hmac-sha2-256,hmac-sha1
debug2: compression ctos: zlib,none
debug2: compression stoc: zlib,none
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: ecdh-sha2-nistp256
debug1: kex: host key algorithm: ecdsa-sha2-nistp384
debug1: kex: server->client cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug1: kex: client->server cipher: aes128-ctr MAC: hmac-sha2-256 compression: none
debug3: send packet: type 30
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug3: receive packet: type 31
debug1: Server host key: ecdsa-sha2-nistp384 SHA256:kNkp4TIDsSbswddevanXAPgmtwXotVY4aojuRxZmOag
debug3: hostkeys_foreach: reading file "/home/daniel/.ssh/known_hosts"
debug3: record_hostkey: found key type ECDSA in file /home/daniel/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys from 192.168.1.31
debug1: Host '192.168.1.31' is known and matches the ECDSA host key.
debug1: Found key in /home/daniel/.ssh/known_hosts:1
debug3: send packet: type 21
debug2: set_newkeys: mode 1
debug1: rekey after 4294967296 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug3: receive packet: type 21
debug1: SSH2_MSG_NEWKEYS received
debug2: set_newkeys: mode 0
debug1: rekey after 4294967296 blocks
debug2: key: /home/daniel/.ssh/id_rsa (0x55cab80f3c40), agent
debug2: key: [email protected] (0x55cab80f7e90), agent
debug2: key: /home/daniel/.ssh/id_dsa ((nil))
debug2: key: /home/daniel/.ssh/id_ecdsa ((nil))
debug2: key: /home/daniel/.ssh/id_ed25519 ((nil))
debug3: send packet: type 5
debug3: receive packet: type 7
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<ecdsa-sha2-1.3.132.0.10,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,rsa-sha2-512,rsa-sha2-256,ssh-rsa>
debug3: receive packet: type 6
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug3: send packet: type 50
debug3: receive packet: type 51
debug1: Authentications that can continue: publickey,gssapi-with-mic,password
debug3: start over, passed a different list publickey,gssapi-with-mic,password
debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
debug3: authmethod_lookup gssapi-with-mic
debug3: remaining preferred: publickey,keyboard-interactive,password
debug3: authmethod_is_enabled gssapi-with-mic
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure.  Minor code may provide more information
No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_1000)

debug1: Unspecified GSS failure.  Minor code may provide more information
No Kerberos credentials available (default cache: FILE:/tmp/krb5cc_1000)

debug2: we did not send a packet, disable method
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/daniel/.ssh/id_rsa
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: pkalg rsa-sha2-512 blen 535
debug2: input_userauth_pk_ok: fp SHA256:RZPLPu6tVldvSOMjzGq+57kt60onH4zTtiYmpQrWw9Y
debug3: sign_and_send_pubkey: RSA SHA256:RZPLPu6tVldvSOMjzGq+57kt60onH4zTtiYmpQrWw9Y
debug3: send packet: type 50
debug3: receive packet: type

서버 응답

Authentication attempt from 192.168.2.1:38794 with user name 'dn' suceeded partially. The public key supplied has been verified; requesting signature.
Authentication attempt from 192.168.2.1:38794 with user name 'dn' failed. Signature verification failed
Authentication attempt from 192.168.2.1:38794 with user name 'dn' suceeded partially. The public key supplied has been verified; requesting signature.
Authentication attempt from 192.168.2.1:38794 with user name 'dn' failed. Signature verification failed

답변1

클라이언트의 관점에서 중요한 것은 로그의 다음 부분입니다.

debug1: Offering RSA public key: /home/daniel/.ssh/id_rsa
debug3: send_pubkey_test
debug3: send packet: type 50
debug2: we sent a publickey packet, wait for reply
debug3: receive packet: type 60
debug1: Server accepts key: pkalg rsa-sha2-512 blen 535
debug2: input_userauth_pk_ok: fp SHA256:RZPLPu6tVldvSOMjzGq+57kt60onH4zTtiYmpQrWw9Y
debug3: sign_and_send_pubkey: RSA SHA256:RZPLPu6tVldvSOMjzGq+57kt60onH4zTtiYmpQrWw9Y
debug3: send packet: type 50

첫 번째 라인은 실제 공개 키를 제공하고 여섯 번째 라인은 패킷 60을 수신합니다.SSH2_MSG_USERAUTH_PK_OK(서버의 첫 번째 디버그 라인에 해당) 그런 다음 PK 알고리즘을 사용하여 실제 서명을 보내지 rsa-sha2-512만 거부됩니다(응답 패킷이 로그에서 제거됨). 이는 서버의 두 번째 줄을 나타냅니다. 서명 확인에 실패했습니다.

OpenSSH의 SHA2 확장에 버그가 있습니다. 이미 신고했어요버그 #2799, OpenSSH가 아닌 다른 것을 사용하는 경우 이는 ssh-agent와의 통신에 영향을 미칩니다. 귀하의 문제와 직접 관련이 있습니다.

내가 아는 한, 당신은 다른 것을 사용하고 있으며(gnome-keyring의 출력은 무엇입니까? echo $SSH_AUTH_SOCK) 서버는 해당 에이전트가 제공한 오류 서명을 받아들이지 않습니다. 난 이미 하나를 다 채웠어그놈 키링 오류거기서 문제는 해결됐지만 그놈 버전으로 들어가려면 시간이 좀 걸릴 것 같습니다.

따라서 지금으로서는 ssh-agent를 사용하거나 에이전트를 전혀 사용하지 않는 것이 가장 좋습니다. 다음 명령을 실행하면 서버로 이동됩니다.

SSH_AUTH_SOCK='' ssh [email protected]

gnome-keyring을 패치하거나 마스터에서 빌드할 수도 있습니다(일부 추가 작업). ECDSA 키도 사용할 수 있어야 하지만 아직 게시된 gnome-keyring에는 없습니다.

관련 정보