![]() > client software version WinSCP_release_5.15.2 Removing read permission (only permission) for this user again gives the old error, saying Access Denied.ĮDIT - sshd.exe Logs from a connection attempt : > 2696 03:57:09.020 debug2: fd 3 setting O_NONBLOCK But now, a connection attempt complains that bad permission has been set for user S-1-5-80 which is the same NT Service user sshd added by Repair-AutorizedKeyFile. ![]() I tried using Repair-AuthorizedKeyPermission on the key file, which added SYSTEM and sshd (NT Service user) as users to the key file, sshd having read access. ssh folder of that user only that one user access. The machine only has one user, and the authorized_keys within the. # AuthorizedKeysFile _PROGRAMDATA_/ssh/administrators_authorized_keysīut now, a connection attempt complains that authorized_keys has bad permission. I commented out the following in sshd_config: #Match Group administrators Should it run under a user account (I tried that but the service does not start at all, Event logs complain of a missing privilege.) The sshd service is running under LOCAL SYSTEM account. There's only one user on the server machine, which is the logged in user. Is the key generated by PuTTy (or the key content copied with public key) not supported in either place? There's no passphrase associated with the key, but I don't suppose that should be an issue. The client machine, and WinScp are being recognized on the server, it's just that the server refuses the provided key. Firewall cannot be an issue since I am able to log into the server using password authentication. I am not sure what happened here, and if this is the reason why connection was refused. ![]() Digging through the sshd logs generated on the server, I see this: 10200 01:38:16.376 debug1: attempt 1 failures 0 ġ0200 01:38:16.376 debug2: input_userauth_request: try method publickey ġ0200 01:38:16.376 debug1: userauth_pubkey: test pkalg ssh-rsa pkblob RSA SHA256:B6s0omPbz6HJB2cIZf3 5MKHU42wp JfOTyAM EVqoY ġ0200 01:38:16.376 debug2: userauth_pubkey: disabled because of invalid user I am able to authenticate using password, but the key pair isn't working out. PPK private key, with WinSCP to try and connect into an SFTP session with my server, but I get a message that the server refused the key which I had selected. I fixed file permissions as required, to only my user, i.e., the logged in user, for the key file. ssh\authorized_keys file of my SSH server user. I copied the public key portion and appended that to the. ![]() On another machine, I have used WinSCP and PuTTy generator to generate an authentication key. On Windows 10 1809, I have enabled the in-built SSH server, and have configured it. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |