SSH daemon is not reading authorized_keys #242
Comments
|
This is the command I'm connecting with from a Linux machine: |
|
When I run the ssh agent manually from the command line I get: |
|
Even when running under cmd as |
|
I'm now trying a previous version with: |
|
Now I'm getting: These logs are from sshd running as a service (I set LogLevel to DEBUG). As I restarted my computer after running |
|
So I ran the same query that This is from running and writing out The third option in that list, |
|
I ran the following to update the registry key for anyone else having this problem who visited this task: |
|
Well now I'm getting further, though my NoMachine client can't connect any more which is inconvenient to say the least... |
|
Oh, looks like I had left in My guess is that either the Win32 OpenSSH install scripts do weird things when NoMachine has installed it's authentication provider, and that they're (at least for the moment), incompatible. Once you install the SSH-LSA provider, it doesn't look like NoMachine is able to open any more sessions (even when it's listed as the second authentication provider). |
|
Just an FYI on this thread - i do not test the package for downgrade - so it would be more reliable to do an uninstall and reinstall to move backward. That said - since the commands that move the files in place are copies with overwrite - it might be reliable to downgrade - but I haven't specifically engineered it for downgrade and don't current test it for that. |
|
@hach-que, this thread has become to long to consume :). Can you please summarize what you've found so far and what needs to be looked into? Reopen once you do that please. |
This is the output of
sshd.exe -dddwhen running it under the same user that I'm trying to login as. I've already given it the correct privileges as I can perform password authentication fine, but SSH authentication keeps getting rejected:It seems the SSH authentication is rejected, but it doesn't appear to be attempting to read
authorized_keysat all? I haveC:\Users\Build\.ssh\authorized_keysand have given theNT SERVICE\sshdaccount access to read that file and the.sshdirectory.The text was updated successfully, but these errors were encountered: