-
Notifications
You must be signed in to change notification settings - Fork 738
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
user resolution fails inconsistently #1666
Comments
Is the user name the same as the machine name? |
No, but I saw that bug too. :) In fact I can reproduce this with multiple users. |
Can you try with 8.1? I feel like we normally see more output relative to name resolution. Can't remember when I added that code. |
Er, I just installed the Windows Capability |
Installation instructions are here: https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH |
Will do. In the meantime, I think I have more data. It's not domain-vs-not-domain. It seems to be Windows 10 vs other things. I can repro this on a machine joined to the domain that has an older version of openssh (7.7.2.3). But what's weird is I actually see MORE logs around resolving the user:
EDIT TO ADD: Here's what happens when I do debug3, it somehow does NOT print those LookupACcountName logs...
weird... |
8.1.0-p1 beta seems to reliably map the user well.... |
Turns out 8.0.0.1 from chocolately also seems to work well. Just not the one from WindowsCapability. |
I went back and forth between these 3 versions repeatedly, and it's consistent. The WindowsCapability version fails to resolve users quite often, but the chocolatey version and the latest build from GH both work reliably. |
@bagajjal / @NoMoreFood - I don't mind closing this - as a developer, I understand the box is clearly fixed in modern versions of the code, but out of curiousity, do you know what the process/schedule is for getting a newer version of SSH into the WindowsCapability ... repo, for lack of a better term? |
The new windows update coming next month will have latest github version binaries. |
awesome, thanks! |
Troubleshooting steps
"OpenSSH for Windows" version
Server OperatingSystem
Windows 10 Pro
Client OperatingSystem
Ubuntu 18.0.4
What is failing
When sshing to the server, about half the time the user fails to resolve. It's worth noting the user (all users) are local.
Trying the same command 2 or 3 times will succeed, but it fails several times with what the server sees as:
Expected output
I'm stopping it here because the failure doesn't get half that far, but can provide more.
Actual output
If I then put in a password (even though key auth usually works) it will fail, and I get this additional output
If keys fail, password fails, for the same reason, "invalud user"
But it was able to map me a moment ago and again on the next try.
Other Info
The same exact setup on machines that are attached to a domain don't seem to have this issue at all. The identical setup on both win2k16 server and win10 works fine on domain-ified machines, but standalone machines with local users seem to have this issue.
The text was updated successfully, but these errors were encountered: