-
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
Unable to connect with public key #175
Comments
What's the key type? Currently only RSA keys work for client key-based authentication. |
I ran the keygen -t RSA command which created the id_rsa and id_rsa.pub. For WinSCP I did have to run the Putty conversion, but again, still resulted in the same error. Seems permissions related, but I'm unsure where to begin when I'm using local admin. |
error 1300 maps to "Not all privileges or groups referenced are assigned to the caller." I believe you are trying to run sshd.exe interactively. Instead try installing it as a service (see wiki for instructions). That should fix your issue. |
I am running it as a service. As Local System (default when installing as service), I receive this error: SSH-LSA package not found. (err = 0, ntStat = c00000fe). When I switch service to Local Admin, I'm receiving the OP error: Cannot logon using LSA package (err = 1300, ntStat = c0000041) This is a brand new deployed 2012R2 server, nothing else loaded and fully patched. I'm just confused that it seems permissions related, but local admin has all the rights that I can see. Clearly I'm missing something, but followed wiki line by line. I also just deployed the latest package, but still the exact same error. |
+1 Can't seem to figure this out. If I was on a *nix system I would I installed release 4_5_2016 today on a Windows7 64bit laptop. Attached are my client & server debugs; any ideas/suggestions? |
Well, I was also unable to connect using the public key method. Copied the public key %systemdrive%\users\user.ssh\authorized_keys and tried to connect but public key auth was skipped and password auth was taken. Then I found a hint on the net stating that this is because of the sshd being started as a service by Local System account which can't read the users authorized_keys file. Solution: stop the service and start sshd by hand as that user who tries to log into the machine. That's what I successfully did. That does not seem like a good solution but maybe it helps on fixing that problem for devs and users ... |
After many hours of trying to get public key authentication working and seeing the same error "SSH-LSA package not found" I have finally made it. The problem was, that I have installed (unpacked) the zip to C:\OpenSSH-Win32 and not to the recommended 'Program Files'. I did follow all the other installation steps and the installation was succesfull, except for the key authentication not working. I have checked the registry and the ssh-lsa part was where it was supposed to be, ssh-lsa.dll was in c:\windows\system32, everything seemed to be OK... but it didn't work. The simple solution was to uninstall everything and reinstall to C:\Program Files\OpenSSH-Win64, with the required reboot after installation of sshlsa. |
Reopen if you still see issues with latest release. Now domain accounts too are supported. |
Hi, this is still failing for me in (5_15_2016); but the log message (
Any ideas to why Basic checks completed:
Footnote: I |
I have the same problem, and I think I've gone through the same verification steps as above. |
#253 Seems like a new issue was already created |
For the record: I could fix my public key authentication problems following the suggestion from @SkyRider64 and reinstalling Win32-OpenSSH in |
I'm new to OpenSSH - followed the documentation, but I'm unable to get public key accepted. I'm able to log in locally and remotely using the users password, so functionality is fine, it's just the public key auth that is not working. This is a Windows 2012 R2 server with the latest build OpenSSH (using 1.1 because other version resulted in service not starting)
When I use SSH - it prompts for passphrase for private key, but then moves on to ask for user password. The log states:
Cannot logon using LSA package (err = 1300, ntStat = c0000041)
If I try and use WinSCP, I get the message after entering the passphrase: 'Server refused public-key signature despite accepting key' with the same corresponding error being logged:
Cannot logon using LSA package (err = 1300, ntStat = c0000041)
Right now, I'm using an admin privileged user (I've tried running service as admin and local system). This is not a part of a domain.
RSAAuthentication and PubkeyAuthentication set to yes (and uncommented)
Issue similar to this post - #87 - but I do not have any active policies set.
The text was updated successfully, but these errors were encountered: