どのユーザーも、キーを使用して最近アップグレードされたCentOS 7システムにSSH経由でアクセスできません。

どのユーザーも、キーを使用して最近アップグレードされたCentOS 7システムにSSH経由でアクセスできません。

CentOS 7にアップグレードしたばかりの2台のサーバーがあります。その後、どのユーザーもSSHアクセスにキーを使用できないため、常にパスワードが必要です。
これは他のサーバーでは発生せず、同じマシンでCentOS 6を使用しても発生しません。 .sshディレクトリと最も一般的な認証フォルダに対する権限を確認した後、Googleで問題を検出したときに、.ssh内のすべてのファイルが正しいユーザーが所有していることがわかりました。

GoogleやStackExchangeの他の答えはどちらもオタナ権限の問題に帰結するので役に立ちませんでした。出力は、この質問で提供されているものと非常によく似ています。このユーザーのSSH鍵認証が失敗するのはなぜですか? (セントース7))、しかし、ssh-copy-idを使用すると権限エラーが発生しないため、それらに効果があったソリューションは私たちには効果がありません。

誰のアイデアや提案がありますか?

編集:追加関連情報:

  • 更新されたサーバーはOpenSSH_7.4を実行しており、人々がSSHを試みる他のサーバーはOpenSSH_5.3を実行しています。
  • これはssh -vvv出力です(編集済み)。 OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to {servername} [159.28.23.7] port 22. debug1: Connection established. debug1: identity file /{home directory}/{username}/.ssh/identity type -1 debug1: identity file /{home directory}/{username}/.ssh/identity-cert type -1 debug3: Not a RSA1 key file /{home directory}/{username}/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: identity file /{home directory}/{username}/.ssh/id_rsa type 1 debug1: identity file /{home directory}/{username}/.ssh/id_rsa-cert type -1 debug1: identity file /{home directory}/{username}/.ssh/id_dsa type -1 debug1: identity file /{home directory}/{username}/.ssh/id_dsa-cert type -1 debug1: identity file /{home directory}/{username}/.ssh/id_ecdsa type -1 debug1: identity file /{home directory}/{username}/.ssh/id_ecdsa-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4 debug1: match: OpenSSH_7.4 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 3 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 864 bytes for a total of 885 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],[email protected],ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,[email protected] debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,[email protected] debug2: kex_parse_kexinit: hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[email protected],hmac-sha1-96 debug2: kex_parse_kexinit: hmac-sha1,[email protected],hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,[email protected],hmac-sha1-96 debug2: kex_parse_kexinit: none,[email protected],zlib debug2: kex_parse_kexinit: none,[email protected],zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: 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,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 debug2: kex_parse_kexinit: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,cast128-cbc,3des-cbc debug2: kex_parse_kexinit: [email protected],aes128-ctr,aes192-ctr,aes256-ctr,[email protected],[email protected],aes128-cbc,aes192-cbc,aes256-cbc,blowfish-cbc,cast128-cbc,3des-cbc debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: kex_parse_kexinit: [email protected],[email protected],[email protected],[email protected],[email protected],[email protected],[email protected],hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: kex_parse_kexinit: none,[email protected] debug2: kex_parse_kexinit: none,[email protected] debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-sha1 debug1: kex: server->client aes128-ctr hmac-sha1 none debug2: mac_setup: found hmac-sha1 debug1: kex: client->server aes128-ctr hmac-sha1 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<2048<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 909 debug2: dh_gen_key: priv key bits set: 152/320 debug2: bits set: 1019/2048 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 272 bytes for a total of 1181 debug3: check_host_in_hostfile: host {servername} filename /{home directory}/{username}/.ssh/known_hosts debug3: check_host_in_hostfile: host {servername} filename /{home directory}/{username}/.ssh/known_hosts debug3: check_host_in_hostfile: match line 1 debug3: check_host_in_hostfile: host 159.28.23.7 filename /{home directory}/{username}/.ssh/known_hosts debug3: check_host_in_hostfile: host 159.28.23.7 filename /{home directory}/{username}/.ssh/known_hosts debug3: check_host_in_hostfile: match line 1 debug1: Host '{servername}' is known and matches the RSA host key. debug1: Found key in /{home directory}/{username}/.ssh/known_hosts:1 debug2: bits set: 1035/2048 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 1197 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 52 bytes for a total of 1249 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /{home directory}/{username}/.ssh/identity ((nil)) debug2: key: /{home directory}/{username}/.ssh/id_rsa (0x7f769e632270) debug2: key: /{home directory}/{username}/.ssh/id_dsa ((nil)) debug2: key: /{home directory}/{username}/.ssh/id_ecdsa ((nil)) debug3: Wrote 84 bytes for a total of 1333 debug1: Authentications that can continue: publickey,password debug3: start over, passed a different list publickey,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /{home directory}/{username}/.ssh/identity debug3: no such identity: /{home directory}/{username}/.ssh/identity debug1: Offering public key: /{home directory}/{username}/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 628 bytes for a total of 1961 debug1: Authentications that can continue: publickey,password debug1: Trying private key: /{home directory}/{username}/.ssh/id_dsa debug3: no such identity: /{home directory}/{username}/.ssh/id_dsa debug1: Trying private key: /{home directory}/{username}/.ssh/id_ecdsa debug3: no such identity: /{home directory}/{username}/.ssh/id_ecdsa debug2: we did not send a packet, disable method debug3: authmethod_lookup password debug3: remaining preferred: ,password debug3: authmethod_is_enabled password debug1: Next authentication method: password

編集2:これはローカルユーザーには発生せず、すべてのサーバー間で共有される場所にユーザーディレクトリを持つユーザーにのみ発生するようです。

答え1

解決策は最終的にPAM自体とほとんど関係がありません。問題は実際にSELinuxとの相互作用です。私たちは通常SELinuxを使用していませんが、基本的にSELinuxがインストールされアクティブになっていると思いました。許可モードに設定すると、問題はすぐに解決され、ユーザーはキーを再利用できました。

関連情報