ssh public key authentication not working
I had my keys set up so I can ssh between machines without having to enter a password and everything was working for a while but then, all of a sudden, I'm being prompted for a password on some machines.
I verified the keys - everything appears to be OK. I ran ssh -v and here is the output. From what I can tell, the key is being verified successfully, so why am I asked to enter a password???
ssh XXX.XXX.XXX.XXX -v
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX] port 22.
debug1: Connection established.
debug1: identity file /nethome/username/.ssh/identity type -1
debug1: identity file /nethome/username/.ssh/id_rsa type 1
debug1: identity file /nethome/username/.ssh/id_dsa type 2
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'XXX.XXX.XXX.XXX' is known and matches the RSA host key.
debug1: Found key in /nethome/username/.ssh/known_hosts:43
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Next authentication method: publickey
debug1: Trying private key: /nethome/username/.ssh/identity
debug1: Offering public key: /nethome/username/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Offering public key: /nethome/username/.ssh/id_dsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: password
By the way, I don't see a message that server accepted the authentication:
debug1: Server accepts key: pkalg ssh-rsa blen 277
~/.ssh/ has mode 700, I tried running ssh-copy-id and that seems to have worked.
Just to be sure, I ran md5sum on id_rsa.pub on both machines and they are the same.
Also, the checksum on authorized_keys on the target machine, matches to the checksum of the public key (since it's the only key in authorized keys).
ssh rhel public-key-authentication
asked Oct 7 '14 at 21:24
ventsyv
4342718
add a comment |
I had my keys set up so I can ssh between machines without having to enter a password and everything was working for a while but then, all of a sudden, I'm being prompted for a password on some machines.
I verified the keys - everything appears to be OK. I ran ssh -v and here is the output. From what I can tell, the key is being verified successfully, so why am I asked to enter a password???
ssh XXX.XXX.XXX.XXX -v
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX] port 22.
debug1: Connection established.
debug1: identity file /nethome/username/.ssh/identity type -1
debug1: identity file /nethome/username/.ssh/id_rsa type 1
debug1: identity file /nethome/username/.ssh/id_dsa type 2
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'XXX.XXX.XXX.XXX' is known and matches the RSA host key.
debug1: Found key in /nethome/username/.ssh/known_hosts:43
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Next authentication method: publickey
debug1: Trying private key: /nethome/username/.ssh/identity
debug1: Offering public key: /nethome/username/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Offering public key: /nethome/username/.ssh/id_dsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: password
By the way, I don't see a message that server accepted the authentication:
debug1: Server accepts key: pkalg ssh-rsa blen 277
~/.ssh/ has mode 700, I tried running ssh-copy-id and that seems to have worked.
Just to be sure, I ran md5sum on id_rsa.pub on both machines and they are the same.
Also, the checksum on authorized_keys on the target machine, matches to the checksum of the public key (since it's the only key in authorized keys).
ssh rhel public-key-authentication
asked Oct 7 '14 at 21:24
ventsyv
4342718
The term firewall comes to mind here....or at least iptables on one or the other hosts.
– mdpc
Oct 7 '14 at 22:00
Are you using SE Linux? Also I assume the permissions are actually: chmod 700 ~/.ssh && chmod 600 ~/.ssh/* (check it's like this on the machines that aren't working)
– rainkinz
Oct 7 '14 at 22:58
I'm using different version of RHEL (5.8 and 6.4 mostly). Pretty sure it's just off the shelf RHEL distro. The .pub files, as well as known_hosts are 644, authorized_keys is 640, the private keys (on the machines that have them) are all 600.
– ventsyv
Oct 8 '14 at 18:57
The key that is successfully verified is the server's host key - your own private key is not being verified successfully. Do you have access to the sshd logs of the remote server? Also, what are the permissions of your own home directory on the remote server?
– Jenny D
Oct 13 '14 at 7:34
add a comment |
I had my keys set up so I can ssh between machines without having to enter a password and everything was working for a while but then, all of a sudden, I'm being prompted for a password on some machines.
I verified the keys - everything appears to be OK. I ran ssh -v and here is the output. From what I can tell, the key is being verified successfully, so why am I asked to enter a password???
ssh XXX.XXX.XXX.XXX -v
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX] port 22.
debug1: Connection established.
debug1: identity file /nethome/username/.ssh/identity type -1
debug1: identity file /nethome/username/.ssh/id_rsa type 1
debug1: identity file /nethome/username/.ssh/id_dsa type 2
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'XXX.XXX.XXX.XXX' is known and matches the RSA host key.
debug1: Found key in /nethome/username/.ssh/known_hosts:43
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Next authentication method: publickey
debug1: Trying private key: /nethome/username/.ssh/identity
debug1: Offering public key: /nethome/username/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Offering public key: /nethome/username/.ssh/id_dsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: password
By the way, I don't see a message that server accepted the authentication:
debug1: Server accepts key: pkalg ssh-rsa blen 277
~/.ssh/ has mode 700, I tried running ssh-copy-id and that seems to have worked.
Just to be sure, I ran md5sum on id_rsa.pub on both machines and they are the same.
Also, the checksum on authorized_keys on the target machine, matches to the checksum of the public key (since it's the only key in authorized keys).
ssh rhel public-key-authentication
asked Oct 7 '14 at 21:24
ventsyv
4342718
I had my keys set up so I can ssh between machines without having to enter a password and everything was working for a while but then, all of a sudden, I'm being prompted for a password on some machines.
I verified the keys - everything appears to be OK. I ran ssh -v and here is the output. From what I can tell, the key is being verified successfully, so why am I asked to enter a password???
ssh XXX.XXX.XXX.XXX -v
OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to XXX.XXX.XXX.XXX [XXX.XXX.XXX.XXX] port 22.
debug1: Connection established.
debug1: identity file /nethome/username/.ssh/identity type -1
debug1: identity file /nethome/username/.ssh/id_rsa type 1
debug1: identity file /nethome/username/.ssh/id_dsa type 2
debug1: loaded 3 keys
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_4.3
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'XXX.XXX.XXX.XXX' is known and matches the RSA host key.
debug1: Found key in /nethome/username/.ssh/known_hosts:43
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-with-mic
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Unspecified GSS failure. Minor code may provide more information
No credentials cache found
debug1: Next authentication method: publickey
debug1: Trying private key: /nethome/username/.ssh/identity
debug1: Offering public key: /nethome/username/.ssh/id_rsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Offering public key: /nethome/username/.ssh/id_dsa
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: password
By the way, I don't see a message that server accepted the authentication:
debug1: Server accepts key: pkalg ssh-rsa blen 277
~/.ssh/ has mode 700, I tried running ssh-copy-id and that seems to have worked.
Just to be sure, I ran md5sum on id_rsa.pub on both machines and they are the same.
Also, the checksum on authorized_keys on the target machine, matches to the checksum of the public key (since it's the only key in authorized keys).
ssh rhel public-key-authentication
ssh rhel public-key-authentication
asked Oct 7 '14 at 21:24
ventsyv
4342718
asked Oct 7 '14 at 21:24
ventsyv
4342718
edited Oct 7 '14 at 21:46
asked Oct 7 '14 at 21:24
ventsyv
4342718
asked Oct 7 '14 at 21:24
ventsyv
4342718
asked Oct 7 '14 at 21:24
ventsyv
4342718
4342718
The term firewall comes to mind here....or at least iptables on one or the other hosts.
– mdpc
Oct 7 '14 at 22:00
Are you using SE Linux? Also I assume the permissions are actually: chmod 700 ~/.ssh && chmod 600 ~/.ssh/* (check it's like this on the machines that aren't working)
– rainkinz
Oct 7 '14 at 22:58
I'm using different version of RHEL (5.8 and 6.4 mostly). Pretty sure it's just off the shelf RHEL distro. The .pub files, as well as known_hosts are 644, authorized_keys is 640, the private keys (on the machines that have them) are all 600.
– ventsyv
Oct 8 '14 at 18:57
The key that is successfully verified is the server's host key - your own private key is not being verified successfully. Do you have access to the sshd logs of the remote server? Also, what are the permissions of your own home directory on the remote server?
– Jenny D
Oct 13 '14 at 7:34
add a comment |
The term firewall comes to mind here....or at least iptables on one or the other hosts.
– mdpc
Oct 7 '14 at 22:00
Are you using SE Linux? Also I assume the permissions are actually: chmod 700 ~/.ssh && chmod 600 ~/.ssh/* (check it's like this on the machines that aren't working)
– rainkinz
Oct 7 '14 at 22:58
I'm using different version of RHEL (5.8 and 6.4 mostly). Pretty sure it's just off the shelf RHEL distro. The .pub files, as well as known_hosts are 644, authorized_keys is 640, the private keys (on the machines that have them) are all 600.
– ventsyv
Oct 8 '14 at 18:57
The key that is successfully verified is the server's host key - your own private key is not being verified successfully. Do you have access to the sshd logs of the remote server? Also, what are the permissions of your own home directory on the remote server?
– Jenny D
Oct 13 '14 at 7:34
The term firewall comes to mind here....or at least iptables on one or the other hosts.
– mdpc
Oct 7 '14 at 22:00
The term firewall comes to mind here....or at least iptables on one or the other hosts.
– mdpc
Oct 7 '14 at 22:00
Are you using SE Linux? Also I assume the permissions are actually: chmod 700 ~/.ssh && chmod 600 ~/.ssh/* (check it's like this on the machines that aren't working)
– rainkinz
Oct 7 '14 at 22:58
Are you using SE Linux? Also I assume the permissions are actually: chmod 700 ~/.ssh && chmod 600 ~/.ssh/* (check it's like this on the machines that aren't working)
– rainkinz
Oct 7 '14 at 22:58
I'm using different version of RHEL (5.8 and 6.4 mostly). Pretty sure it's just off the shelf RHEL distro. The .pub files, as well as known_hosts are 644, authorized_keys is 640, the private keys (on the machines that have them) are all 600.
– ventsyv
Oct 8 '14 at 18:57
I'm using different version of RHEL (5.8 and 6.4 mostly). Pretty sure it's just off the shelf RHEL distro. The .pub files, as well as known_hosts are 644, authorized_keys is 640, the private keys (on the machines that have them) are all 600.
– ventsyv
Oct 8 '14 at 18:57
The key that is successfully verified is the server's host key - your own private key is not being verified successfully. Do you have access to the sshd logs of the remote server? Also, what are the permissions of your own home directory on the remote server?
– Jenny D
Oct 13 '14 at 7:34
The key that is successfully verified is the server's host key - your own private key is not being verified successfully. Do you have access to the sshd logs of the remote server? Also, what are the permissions of your own home directory on the remote server?
– Jenny D
Oct 13 '14 at 7:34
add a comment |
2 Answers
2
active
oldest
votes
Turns out that not only .ssh but $HOME permissions matter! $HOME has to have permissions set no higher than 751.
answered Jan 22 '15 at 21:37
ventsyv
4342718
add a comment |
My $HOME permissions seems permissions are 711 and still I am facing the same issue that @ventsyv is facing. My ~/.ssh dir has 700 permissions. What else can be the issue? Please help
answered 18 mins ago
Eega Avinash
1
New contributor
Eega Avinash is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f159915%2fssh-public-key-authentication-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Turns out that not only .ssh but $HOME permissions matter! $HOME has to have permissions set no higher than 751.
answered Jan 22 '15 at 21:37
ventsyv
4342718
add a comment |
Turns out that not only .ssh but $HOME permissions matter! $HOME has to have permissions set no higher than 751.
answered Jan 22 '15 at 21:37
ventsyv
4342718
add a comment |
Turns out that not only .ssh but $HOME permissions matter! $HOME has to have permissions set no higher than 751.
answered Jan 22 '15 at 21:37
ventsyv
4342718
Turns out that not only .ssh but $HOME permissions matter! $HOME has to have permissions set no higher than 751.
answered Jan 22 '15 at 21:37
ventsyv
4342718
answered Jan 22 '15 at 21:37
ventsyv
4342718
answered Jan 22 '15 at 21:37
ventsyv
4342718
answered Jan 22 '15 at 21:37
ventsyv
4342718
4342718
add a comment |
add a comment |
My $HOME permissions seems permissions are 711 and still I am facing the same issue that @ventsyv is facing. My ~/.ssh dir has 700 permissions. What else can be the issue? Please help
answered 18 mins ago
Eega Avinash
1
New contributor
Eega Avinash is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
My $HOME permissions seems permissions are 711 and still I am facing the same issue that @ventsyv is facing. My ~/.ssh dir has 700 permissions. What else can be the issue? Please help
answered 18 mins ago
Eega Avinash
1
New contributor
Eega Avinash is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
My $HOME permissions seems permissions are 711 and still I am facing the same issue that @ventsyv is facing. My ~/.ssh dir has 700 permissions. What else can be the issue? Please help
answered 18 mins ago
Eega Avinash
1
New contributor
Eega Avinash is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
My $HOME permissions seems permissions are 711 and still I am facing the same issue that @ventsyv is facing. My ~/.ssh dir has 700 permissions. What else can be the issue? Please help
answered 18 mins ago
Eega Avinash
1
New contributor
Eega Avinash is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 18 mins ago
Eega Avinash
1
New contributor
Eega Avinash is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 18 mins ago
Eega Avinash
1
answered 18 mins ago
Eega Avinash
1
1
New contributor
Eega Avinash is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Eega Avinash is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Eega Avinash is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f159915%2fssh-public-key-authentication-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The term firewall comes to mind here....or at least iptables on one or the other hosts.
– mdpc
Oct 7 '14 at 22:00
Are you using SE Linux? Also I assume the permissions are actually: chmod 700 ~/.ssh && chmod 600 ~/.ssh/* (check it's like this on the machines that aren't working)
– rainkinz
Oct 7 '14 at 22:58
I'm using different version of RHEL (5.8 and 6.4 mostly). Pretty sure it's just off the shelf RHEL distro. The .pub files, as well as known_hosts are 644, authorized_keys is 640, the private keys (on the machines that have them) are all 600.
– ventsyv
Oct 8 '14 at 18:57
The key that is successfully verified is the server's host key - your own private key is not being verified successfully. Do you have access to the sshd logs of the remote server? Also, what are the permissions of your own home directory on the remote server?
– Jenny D
Oct 13 '14 at 7:34