Server refused public-key signature despite accepting key - putty
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I used puttygen to generate both my public and private key files (ssh2, 2048 bit). I have set up the settings in putty correctly and it is using the correct private key file. As for the public key, (I am using these keys for root) it is in /root/.ssh/authorized_keys
I have tried using chmod on .ssh to 700 and on authorized_keys to 400. That did not do anything.
I have googled everywhere as well and it seems I cannot find a solution to this, as I've tried most things. I figured asking here might assist me.
Does anyone have any recommendations? Thanks in advance.
edit: here's an ls -ldZ of my .ssh folder and authorized_keys file
drwx------ root root ? /root/.ssh
-rw------- root root ? /root/.ssh/authorized_keys
ssh putty
asked May 13 '16 at 3:06
Joel
615
|
show 3 more comments
up vote
0
down vote
favorite
I used puttygen to generate both my public and private key files (ssh2, 2048 bit). I have set up the settings in putty correctly and it is using the correct private key file. As for the public key, (I am using these keys for root) it is in /root/.ssh/authorized_keys
I have tried using chmod on .ssh to 700 and on authorized_keys to 400. That did not do anything.
I have googled everywhere as well and it seems I cannot find a solution to this, as I've tried most things. I figured asking here might assist me.
Does anyone have any recommendations? Thanks in advance.
edit: here's an ls -ldZ of my .ssh folder and authorized_keys file
drwx------ root root ? /root/.ssh
-rw------- root root ? /root/.ssh/authorized_keys
ssh putty
asked May 13 '16 at 3:06
Joel
615
give more information. what is remote server distro, version. is there any security layer between your client and server? (SELinux, iptables,...). Capture the audit log on your remote server when trying to connect to see any hint. Enable putty debug would be helpful.
– cuongnv23
May 13 '16 at 3:42
It's running CentOS 6.7, and as far as I'm aware there is no security layer blocking anything. Where would I look for the audit log? I tried checking the auth log but it seems to not exist. As far as putty debugging goes, do you want the event log? I checked it and it contained quite a bit of information, but leading up to checking the key not much was helpful.
– Joel
May 13 '16 at 4:11
Trying to ssh from Linux box withssh -vvvcould be helpful, although it can contain some private information to be filtered.
– user140866
May 13 '16 at 7:22
ls -ldZ ~ ~/.ssh ~/.ssh/authorized_keyson server.
– Jakuje
May 13 '16 at 8:29
@Joel you should take a look at file/var/log/audit/audit.log. Also, update your answer with output of command from @Jakuje
– cuongnv23
May 13 '16 at 9:49
|
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I used puttygen to generate both my public and private key files (ssh2, 2048 bit). I have set up the settings in putty correctly and it is using the correct private key file. As for the public key, (I am using these keys for root) it is in /root/.ssh/authorized_keys
I have tried using chmod on .ssh to 700 and on authorized_keys to 400. That did not do anything.
I have googled everywhere as well and it seems I cannot find a solution to this, as I've tried most things. I figured asking here might assist me.
Does anyone have any recommendations? Thanks in advance.
edit: here's an ls -ldZ of my .ssh folder and authorized_keys file
drwx------ root root ? /root/.ssh
-rw------- root root ? /root/.ssh/authorized_keys
ssh putty
asked May 13 '16 at 3:06
Joel
615
I used puttygen to generate both my public and private key files (ssh2, 2048 bit). I have set up the settings in putty correctly and it is using the correct private key file. As for the public key, (I am using these keys for root) it is in /root/.ssh/authorized_keys
I have tried using chmod on .ssh to 700 and on authorized_keys to 400. That did not do anything.
I have googled everywhere as well and it seems I cannot find a solution to this, as I've tried most things. I figured asking here might assist me.
Does anyone have any recommendations? Thanks in advance.
edit: here's an ls -ldZ of my .ssh folder and authorized_keys file
drwx------ root root ? /root/.ssh
-rw------- root root ? /root/.ssh/authorized_keys
ssh putty
ssh putty
asked May 13 '16 at 3:06
Joel
615
asked May 13 '16 at 3:06
Joel
615
edited May 13 '16 at 22:14
asked May 13 '16 at 3:06
Joel
615
asked May 13 '16 at 3:06
Joel
615
asked May 13 '16 at 3:06
Joel
615
615
give more information. what is remote server distro, version. is there any security layer between your client and server? (SELinux, iptables,...). Capture the audit log on your remote server when trying to connect to see any hint. Enable putty debug would be helpful.
– cuongnv23
May 13 '16 at 3:42
It's running CentOS 6.7, and as far as I'm aware there is no security layer blocking anything. Where would I look for the audit log? I tried checking the auth log but it seems to not exist. As far as putty debugging goes, do you want the event log? I checked it and it contained quite a bit of information, but leading up to checking the key not much was helpful.
– Joel
May 13 '16 at 4:11
Trying to ssh from Linux box withssh -vvvcould be helpful, although it can contain some private information to be filtered.
– user140866
May 13 '16 at 7:22
ls -ldZ ~ ~/.ssh ~/.ssh/authorized_keyson server.
– Jakuje
May 13 '16 at 8:29
@Joel you should take a look at file/var/log/audit/audit.log. Also, update your answer with output of command from @Jakuje
– cuongnv23
May 13 '16 at 9:49
|
show 3 more comments
give more information. what is remote server distro, version. is there any security layer between your client and server? (SELinux, iptables,...). Capture the audit log on your remote server when trying to connect to see any hint. Enable putty debug would be helpful.
– cuongnv23
May 13 '16 at 3:42
It's running CentOS 6.7, and as far as I'm aware there is no security layer blocking anything. Where would I look for the audit log? I tried checking the auth log but it seems to not exist. As far as putty debugging goes, do you want the event log? I checked it and it contained quite a bit of information, but leading up to checking the key not much was helpful.
– Joel
May 13 '16 at 4:11
Trying to ssh from Linux box withssh -vvvcould be helpful, although it can contain some private information to be filtered.
– user140866
May 13 '16 at 7:22
ls -ldZ ~ ~/.ssh ~/.ssh/authorized_keyson server.
– Jakuje
May 13 '16 at 8:29
@Joel you should take a look at file/var/log/audit/audit.log. Also, update your answer with output of command from @Jakuje
– cuongnv23
May 13 '16 at 9:49
give more information. what is remote server distro, version. is there any security layer between your client and server? (SELinux, iptables,...). Capture the audit log on your remote server when trying to connect to see any hint. Enable putty debug would be helpful.
– cuongnv23
May 13 '16 at 3:42
give more information. what is remote server distro, version. is there any security layer between your client and server? (SELinux, iptables,...). Capture the audit log on your remote server when trying to connect to see any hint. Enable putty debug would be helpful.
– cuongnv23
May 13 '16 at 3:42
It's running CentOS 6.7, and as far as I'm aware there is no security layer blocking anything. Where would I look for the audit log? I tried checking the auth log but it seems to not exist. As far as putty debugging goes, do you want the event log? I checked it and it contained quite a bit of information, but leading up to checking the key not much was helpful.
– Joel
May 13 '16 at 4:11
It's running CentOS 6.7, and as far as I'm aware there is no security layer blocking anything. Where would I look for the audit log? I tried checking the auth log but it seems to not exist. As far as putty debugging goes, do you want the event log? I checked it and it contained quite a bit of information, but leading up to checking the key not much was helpful.
– Joel
May 13 '16 at 4:11
Trying to ssh from Linux box with
ssh -vvv could be helpful, although it can contain some private information to be filtered.– user140866
May 13 '16 at 7:22
Trying to ssh from Linux box with
ssh -vvv could be helpful, although it can contain some private information to be filtered.– user140866
May 13 '16 at 7:22
ls -ldZ ~ ~/.ssh ~/.ssh/authorized_keys on server.– Jakuje
May 13 '16 at 8:29
ls -ldZ ~ ~/.ssh ~/.ssh/authorized_keys on server.– Jakuje
May 13 '16 at 8:29
@Joel you should take a look at file
/var/log/audit/audit.log. Also, update your answer with output of command from @Jakuje– cuongnv23
May 13 '16 at 9:49
@Joel you should take a look at file
/var/log/audit/audit.log. Also, update your answer with output of command from @Jakuje– cuongnv23
May 13 '16 at 9:49
|
show 3 more comments
3 Answers
3
active
oldest
votes
up vote
1
down vote
Set LogLevel to DEBUG in sshd_config, and I think you'll find (in auth.log of course) a reason why you publick key is refused.
edited May 13 '16 at 9:38
Archemar
19.6k93569
answered May 13 '16 at 8:03
Maxiko
1094
You don't even need to change the log level. A denied login is always logged with a reason, and usually that reason is enough to figure it out.
– Gilles
May 13 '16 at 21:38
add a comment |
up vote
0
down vote
accepted
Looking at the log /var/log/secure showed that it was just downright refused. I'm somewhat new to centos since I'm mainly a debian kind of guy, so I was unaware of /var/log/secure
After checking this and doing a bit of searching, it turns out PermitRootLogin no needs to be PermitRootLogin without-password if you want to specifically use just keys for root login. That did the trick. Thanks everyone for contributing.
answered May 13 '16 at 22:23
Joel
615
add a comment |
up vote
0
down vote
I had this problem seemingly out of nowhere. Previously I'd added ssh keys and connected without issue. Even the SSH button to connect to the VM available through the Google Cloud Console website would fail to register keys.
The problem was that Google's Linux Guest Environment wasn't running. I resolved my issue by following the directions for In-Place Install: Linux Guest Environment.
answered Dec 4 at 20:10
Mark Jones
1
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',
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%2f282908%2fserver-refused-public-key-signature-despite-accepting-key-putty%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
Set LogLevel to DEBUG in sshd_config, and I think you'll find (in auth.log of course) a reason why you publick key is refused.
edited May 13 '16 at 9:38
Archemar
19.6k93569
answered May 13 '16 at 8:03
Maxiko
1094
You don't even need to change the log level. A denied login is always logged with a reason, and usually that reason is enough to figure it out.
– Gilles
May 13 '16 at 21:38
add a comment |
up vote
1
down vote
Set LogLevel to DEBUG in sshd_config, and I think you'll find (in auth.log of course) a reason why you publick key is refused.
edited May 13 '16 at 9:38
Archemar
19.6k93569
answered May 13 '16 at 8:03
Maxiko
1094
You don't even need to change the log level. A denied login is always logged with a reason, and usually that reason is enough to figure it out.
– Gilles
May 13 '16 at 21:38
add a comment |
up vote
1
down vote
up vote
1
down vote
Set LogLevel to DEBUG in sshd_config, and I think you'll find (in auth.log of course) a reason why you publick key is refused.
edited May 13 '16 at 9:38
Archemar
19.6k93569
answered May 13 '16 at 8:03
Maxiko
1094
Set LogLevel to DEBUG in sshd_config, and I think you'll find (in auth.log of course) a reason why you publick key is refused.
edited May 13 '16 at 9:38
Archemar
19.6k93569
answered May 13 '16 at 8:03
Maxiko
1094
edited May 13 '16 at 9:38
Archemar
19.6k93569
edited May 13 '16 at 9:38
Archemar
19.6k93569
edited May 13 '16 at 9:38
Archemar
19.6k93569
19.6k93569
answered May 13 '16 at 8:03
Maxiko
1094
answered May 13 '16 at 8:03
Maxiko
1094
answered May 13 '16 at 8:03
Maxiko
1094
1094
You don't even need to change the log level. A denied login is always logged with a reason, and usually that reason is enough to figure it out.
– Gilles
May 13 '16 at 21:38
add a comment |
You don't even need to change the log level. A denied login is always logged with a reason, and usually that reason is enough to figure it out.
– Gilles
May 13 '16 at 21:38
You don't even need to change the log level. A denied login is always logged with a reason, and usually that reason is enough to figure it out.
– Gilles
May 13 '16 at 21:38
You don't even need to change the log level. A denied login is always logged with a reason, and usually that reason is enough to figure it out.
– Gilles
May 13 '16 at 21:38
add a comment |
up vote
0
down vote
accepted
Looking at the log /var/log/secure showed that it was just downright refused. I'm somewhat new to centos since I'm mainly a debian kind of guy, so I was unaware of /var/log/secure
After checking this and doing a bit of searching, it turns out PermitRootLogin no needs to be PermitRootLogin without-password if you want to specifically use just keys for root login. That did the trick. Thanks everyone for contributing.
answered May 13 '16 at 22:23
Joel
615
add a comment |
up vote
0
down vote
accepted
Looking at the log /var/log/secure showed that it was just downright refused. I'm somewhat new to centos since I'm mainly a debian kind of guy, so I was unaware of /var/log/secure
After checking this and doing a bit of searching, it turns out PermitRootLogin no needs to be PermitRootLogin without-password if you want to specifically use just keys for root login. That did the trick. Thanks everyone for contributing.
answered May 13 '16 at 22:23
Joel
615
add a comment |
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Looking at the log /var/log/secure showed that it was just downright refused. I'm somewhat new to centos since I'm mainly a debian kind of guy, so I was unaware of /var/log/secure
After checking this and doing a bit of searching, it turns out PermitRootLogin no needs to be PermitRootLogin without-password if you want to specifically use just keys for root login. That did the trick. Thanks everyone for contributing.
answered May 13 '16 at 22:23
Joel
615
Looking at the log /var/log/secure showed that it was just downright refused. I'm somewhat new to centos since I'm mainly a debian kind of guy, so I was unaware of /var/log/secure
After checking this and doing a bit of searching, it turns out PermitRootLogin no needs to be PermitRootLogin without-password if you want to specifically use just keys for root login. That did the trick. Thanks everyone for contributing.
answered May 13 '16 at 22:23
Joel
615
answered May 13 '16 at 22:23
Joel
615
answered May 13 '16 at 22:23
Joel
615
answered May 13 '16 at 22:23
Joel
615
615
add a comment |
add a comment |
up vote
0
down vote
I had this problem seemingly out of nowhere. Previously I'd added ssh keys and connected without issue. Even the SSH button to connect to the VM available through the Google Cloud Console website would fail to register keys.
The problem was that Google's Linux Guest Environment wasn't running. I resolved my issue by following the directions for In-Place Install: Linux Guest Environment.
answered Dec 4 at 20:10
Mark Jones
1
add a comment |
up vote
0
down vote
I had this problem seemingly out of nowhere. Previously I'd added ssh keys and connected without issue. Even the SSH button to connect to the VM available through the Google Cloud Console website would fail to register keys.
The problem was that Google's Linux Guest Environment wasn't running. I resolved my issue by following the directions for In-Place Install: Linux Guest Environment.
answered Dec 4 at 20:10
Mark Jones
1
add a comment |
up vote
0
down vote
up vote
0
down vote
I had this problem seemingly out of nowhere. Previously I'd added ssh keys and connected without issue. Even the SSH button to connect to the VM available through the Google Cloud Console website would fail to register keys.
The problem was that Google's Linux Guest Environment wasn't running. I resolved my issue by following the directions for In-Place Install: Linux Guest Environment.
answered Dec 4 at 20:10
Mark Jones
1
I had this problem seemingly out of nowhere. Previously I'd added ssh keys and connected without issue. Even the SSH button to connect to the VM available through the Google Cloud Console website would fail to register keys.
The problem was that Google's Linux Guest Environment wasn't running. I resolved my issue by following the directions for In-Place Install: Linux Guest Environment.
answered Dec 4 at 20:10
Mark Jones
1
answered Dec 4 at 20:10
Mark Jones
1
answered Dec 4 at 20:10
Mark Jones
1
answered Dec 4 at 20:10
Mark Jones
1
1
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%2f282908%2fserver-refused-public-key-signature-despite-accepting-key-putty%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
give more information. what is remote server distro, version. is there any security layer between your client and server? (SELinux, iptables,...). Capture the audit log on your remote server when trying to connect to see any hint. Enable putty debug would be helpful.
– cuongnv23
May 13 '16 at 3:42
It's running CentOS 6.7, and as far as I'm aware there is no security layer blocking anything. Where would I look for the audit log? I tried checking the auth log but it seems to not exist. As far as putty debugging goes, do you want the event log? I checked it and it contained quite a bit of information, but leading up to checking the key not much was helpful.
– Joel
May 13 '16 at 4:11
Trying to ssh from Linux box with
ssh -vvvcould be helpful, although it can contain some private information to be filtered.– user140866
May 13 '16 at 7:22
ls -ldZ ~ ~/.ssh ~/.ssh/authorized_keyson server.– Jakuje
May 13 '16 at 8:29
@Joel you should take a look at file
/var/log/audit/audit.log. Also, update your answer with output of command from @Jakuje– cuongnv23
May 13 '16 at 9:49