-
Notifications
You must be signed in to change notification settings - Fork 768
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
Key generated is not considered by ssh when connecting to server #1387
Comments
Follow trouble shooting steps at If you are an admin, see if this helps: |
Manoj, I followed those instructions. First of all, what is interesting is that I can Enter-PSSession from the win 2k19 sever to Centos but not from Centos to win 2k19.
on win2k19 then switch to centos box, issued
Here is the output on the win 2k19 (I can understand that theres is authentication error but not able to find why), thanks for your help debug2: load_server_config: filename PROGRAMDATA\ssh/sshd_config |
I forgot to mention that doing ssh directly from centos works perfectly |
Manoj, while debugging, I issued the following command on the win server
I get several endpoints as follows (powershell and powershell core v 6.2)
Can this be the source of the error? |
In your latest traces, authentication succeeded, but since sshd is run interactively, there was a failure launching worker processes This is expected. Try doing |
I ran this command on the target win2k19 but getting the following error (what is this psexec?)
|
manoj, I managed to run the service with PSEXEC on the windows server as you indicated with PSEXEC, then from Centos I issue
|
any idea Manoj? |
Subsystem process is exiting immediately. From I believe you are hitting issue detailed in Step 3 in https://docs.microsoft.com/en-us/powershell/scripting/learn/remoting/ssh-remoting-in-powershell-core?view=powershell-6#set-up-on-windows-machine |
Yes, exact, it was step 3, OpenSSH for Windows that prevents spaces from working in subsystem executable paths. I was able to log after eliminating spaces. |
1 last question, when I was troubleshooting, I changed the following item |
"OpenSSH for Windows" version
7.7.2.2
Server OperatingSystem
Win 2019
Client OperatingSystem
win 10 64 bit and Centos 7
What is failing
Keys are not recognized and password always requested
Expected output
when generating a Key with ssh-keygen on client machines or server, transfering it (copying content of .pub file to authorized_keys) to server from client or to client from server , then trying to ssh from client or server, normally it should not ask for password which is not the case, always asking for password
Actual output
server always asking for password
The text was updated successfully, but these errors were encountered: