PublicKey Auth Fail #253
Comments
|
I am having the same issue when using PasswordAuthentication no and PublicKey authentication only. Any help is greatly appreciated |
|
https://github.com/PowerShell/Win32-OpenSSH/wiki/Troubleshooting%20Steps Check and dump ssh-agent.log, it should have info on why key based auth failed |
|
Thanks @manojampalam Ill give it a shot this weekend when i have the time :) |
|
I seem to be getting unable to generate user token from the sshd application in the logs. Any ideas? |
|
Is the user account local or domain? If local, ensure that ssh-lsa is installed. Follow steps in wiki. |
|
I am logging in with the local Administrator account. Also Keep in mind i'm installing the software on the server using chocolatey. @DarwinJS |
|
It is possible that the new method of using the scheduler (rather than psexec) is not properly able to register the keys. Can anyone confirm or give me the steps to confirm when the keys are being registered properly by ssh-add ? |
|
I was able to get public key auth working doing a manual installation steps according to the wiki. The chocolatey package installation is the one that gives me the above issue. Sounds like an issue with the choco package installation scripts |
|
@TraGicCode Did you find out the difference between the chocolatey package installation and the manual one? I have tried the manual installation first and failed at a different stage. (Didn't get sshd to start as a service) Thus I tried the chocolatey packages and those installed fine (with some tweaking) but I can't get public key authentication to work. |
|
No I never got it to work. I'm waiting for the next chocolatey release :/ maybe that will work! Sent via the Samsung GALAXY S® 5, an AT&T 4G LTE smartphone -------- Original message -------- @TraGicCode Did you find out the difference between the chocolatey package installation and the manual one? I have tried the manual installation first and failed at a different stage. (Didn't get sshd to start as a service) Thus I tried the chocolatey packages and those installed fine (with some tweaking) but I can't get public key authentication to work. — |
|
Probably related to DarwinJS/ChocoPackages#8 |
|
@TraGicCode which release did you use for manual installation? I just installed 5_30_2016 but key auth is not working for me |
|
I installed manually, following the instructions, and I am having the same problem. Issue #175 has been closed without a solution. |
|
This should be working now in the latest release (still in moderation). You can try it with:
|
|
I have done a manual install of latest release on sep 17 and i am getting similar issue during public key auth. In the ssh-agent log i see error: debug1: connection io 000000B1C61EEEF0 #bytes:0 state:0 |
|
I'm having this issue too. And, thats really off topic in this issue, but I can't install it from choco as DarwinJS suggested, as it gives out: |
|
@rbertoche - you seem to be using the old package id. Please use the id "openssh" like this: choco install openssh -confirm -params '"/SSHServerFeature"' |
|
I have verified on my server that i am ssh'ing into 'NT Service\sshd' account is added to local security policy to replace primary servcie tokens but i still get the error. |
|
I have installed the latest build (openssh -64 bits) on win2012 R2. I try to ssh from my linux server to windows 2012 R2 server: using command On Mon, Oct 3, 2016 at 3:54 AM Darwin [email protected] wrote:
|
|
This is the sshd.log debug2: input_userauth_request: try method publickey |
|
I don't see the full ssh client command you used, but I had a similar problem. In my configuration the "Log on as" sshd service property was set as "Local system account". Perhaps it should be suggested explicitly in the documentation (Install Instructions or Troubleshooting or SSH Usage Examples) to try the 'DOMAIN\user' combination, when in trouble. I think it would save some headaches. |
|
@felippo that really helped and is now working for me using pubkey authentication to automatically sign in. I agree that this should be explicitly stated somewhere in the documentation. I need to also note using user@host works with password authentication. |
|
If you used the chocolatey package to do this install, then the lack of public key auth was likely the fault of the chocolatey package - it was not properly copying the ssh-lsa.dll on new installs. It is fixed in version 0.0.9.20170308, which as of this moment is still in moderation. It can be pulled before moderation is complete by specifying the version on your chocolately install or upgrade command line. |
|
@JINXz both following formats should work for both password and key based auth. Can you please share sshd.log and ssh-agent.log for success and failure cases? |
|
I'm seeing the same problem with the latest 0.0.11.0. Looking at the logs below, the key is found and matches, but it's not accepted. I assume this is due to the token generation failure in the agent. Agent log: openssh log: |
|
I'm having the same issue with v0.0.11.0 ssh-agent.log (from 'node1' - ssh server) sshd.log (w/ DEBUG) (from 'node1' - ssh server) ssh verbose output from 'node2' - ssh client |
|
I'm guessing the above problems are due to ssh-lsa.dll not being installed. Can you try out 0.0.12.0 (that does not require ssh-lsa.dll anymore)? |
|
@manojampalam I've installed 0.0.12.0, but I still have the same problem. SSHd log is identical, but agent log error is slightly different (the LsaLogonUser line now includes NTSTATUS): |
|
Is it a work group account or a domain account? |
|
It's a domain account. Command line is |
|
For my env (domain controlled ssh-host but user account is local to that machine), installing 0.0.12.0 worked. Thanks a ton @manojampalam |
|
@mayo, if its a domain account, you need to specify the domain prefix, you can use any of the following formats |
|
@manojampalam Thanks, works like charm! |
|
Thanks for this info
I'll try it once I'm back home
How can I tell whether the account I'm currently logged on Windows is a
domain account?
I'm still using homegroups, do they count as a domain? I guess not, but I
used be unable to login
I'll update and try again later with those syntaxes, thanks again!
Em 19 de abr de 2017 13:28, "Manoj Ampalam" <[email protected]>
escreveu:
@mayo <https://github.com/mayo>, if its a domain account, you need to
specify the domain prefix, you can use any of the following formats
ssh -l user@domain ssh-host
or
ssh user@domain@ssh-host
or
ssh domain\user@ssh-host
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#253 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAc3Lj94HChMXSiC9ZpzDZoxRnXg9RpCks5rxjYSgaJpZM4JAGYh>
.
|
|
I'm having issues with domain authentication. Is there anything that needs to be configured in the ssh_config to authenticate to the domain? My debug is below Please help. |
|
Using |
|
Reopen a new issues if you see any more issues with public key authentication. |
ghost
mentioned this issue
Hi,
I tired to connect from a linux client to windows server with OpenSSH and public key authetication.
Here is the debug from the server:
Here is the debug from the client:
Something about my sshd_config:
The "authorized_keys" text file with the id_rsa public key from the linux client is in C:/Users/Administrator/.ssh/
Here the sshd_config:
I hope you can help me
Thank you
The text was updated successfully, but these errors were encountered: