New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Public Key Auth Fails Multiple Ways - Windows to Windows and Linux to Windows #1112
Comments
Try removing "NT Service/sshd". Starting from v1.0.0.0 we don't need this. Please verify these,
|
After removing "NT Service/sshd", got closer, but still no dice. Now it's complaining about a broken pipe and test2\testadmin being a bad user (i.e. From CentOS7 Client to Windows 2102 R2 SSHD Server: SSHD Log (EDIT: Updated with DEBUG3)
SSH Client -vvv Output:
EDIT 2: |
Looks like you are running into a known bug #1098. we suggest to use v1.0.0.0. |
Okay, thanks for your help! |
"OpenSSH for Windows" version
Server OperatingSystem
Client OperatingSystem
Tried from both Windows and CentOS client.
Windows Client Info:
CentOS 7 Client Info:
What is failing
Public key authentication.
Key Creation
Key pairs created and tested with the below command on both Windows and CentOS (with blank password):
Please note, the keys are not a problem...I tested between Linux hosts and they work fine.
Windows 2012 SSHD Server File Permissions:
IMPORTANT NOTE: I also tried with
NT SERVICE\sshd
only havingRead
access onC:\Users\testadmin\.ssh
(as opposed toRead, Synchronize
illustrated above). Result was the same.IMPORTANT NOTE: I also tried with
NT SERVICE\sshd
only havingRead
access onC:\Users\testadmin\.ssh\authorized_keys
(as opposed toRead, Synchronize
illustrated above). Result was the same.Scenario 1: CentOS7 Client to Windows 2012 R2 SSHD Server
SSHD Log
CentOS 7 SSH Client -vvv Output:
NOTE: I should NOT be prompted for a password (but at least it falls back to password...using the password does indeed work). The corresponding public key exists in the file
C:\Users\testadmin\.ssh\authorized_keys
on the Windows 2012 R2 SSHD host.Scenario 2: Windows 2016 Client to Windows 2012 R2 SSHD Server
SSHD Log:
Windows 2016 SSH Client -vvv Output:
NOTE: I don't even get prompted for a password in this scenario (i.e. ssh from Windows 2016 SSH Client to Windows 2012 R2 SSHD Server). Again, the corresponding public key exists in the file
C:\Users\testadmin\.ssh\authorized_keys
on the Windows 2012 R2 SSHD host.The text was updated successfully, but these errors were encountered: