Skip to content
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

[Regression] v7.6.0.0p1-Beta broke certain domain logons #1098

Closed
manojampalam opened this issue Mar 8, 2018 · 4 comments
Closed

[Regression] v7.6.0.0p1-Beta broke certain domain logons #1098

manojampalam opened this issue Mar 8, 2018 · 4 comments
Assignees

Comments

@manojampalam
Copy link
Contributor

manojampalam commented Mar 8, 2018

Please answer the following

If it is a terminal issue then please go through wiki
https://github.com/PowerShell/Win32-OpenSSH/wiki/TTY-PTY-support-in-Windows-OpenSSH

"OpenSSH for Windows" version
v7.6.0.0

Server OperatingSystem
Windows 10 Enterprise

Client OperatingSystem
Windows 10 Enterprise

What is failing
Domain account logons may fail if FQDNN is used or the account does not have permissions to query AD

Expected output
It works

Actual output
Unable to login with debug logs showing failures with the following API call
NetUserGetInfo() failed with error: XXXXX

@manojampalam manojampalam added this to the vNext milestone Mar 8, 2018
@manojampalam manojampalam self-assigned this Mar 8, 2018
@manojampalam manojampalam changed the title [Regression] v7.6.0.0p1-Beta broke certain domain logins [Regression] v7.6.0.0p1-Beta broke certain domain logons Mar 8, 2018
@dwatley
Copy link

dwatley commented Mar 19, 2018

@manojampalam - Is this still on track for next release, and is the next release still targeted for this week? I haven't seen a PR come through yet.

@manojampalam
Copy link
Contributor Author

manojampalam commented Mar 19, 2018

Yes. It was fixed as part of PowerShell/openssh-portable@2c559a2

in file sshd.c

We have a couple of PRs in the pipeline.. Release should be out once they go through.

@dwatley
Copy link

dwatley commented Mar 19, 2018

Ah I missed it since the issue or change wasn't referenced in the commit notes. Thanks for the update, looking forward to testing.

@dwatley
Copy link

dwatley commented Apr 1, 2018

Confirming the latest release fixed this for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants