As you will have troubles running it on Windows, you can run it on the server itself. To avoid common pitfalls when setting up a public key authentication, use ssh-copy-id command/script. 17:43:09 GSSAPI authentication request refused 17:43:09 Attempting GSSAPI authentication 17:43:05 Reading key file "C:\Users\\Desktop\private_key.ppk" 17:43:05 Initialised HMAC-SHA-256 server->client MAC algorithm 17:43:05 Initialised AES-256 SDCTR server->client encryption 17:43:05 Initialised HMAC-SHA-256 client->server MAC algorithm 17:43:05 Initialised AES-256 SDCTR client->server encryption 17:43:05 Server also has ecdsa-sha2-nistp256 host key, but we don't know it 17:43:05 Doing ECDH key exchange with curve Curve25519 and hash SHA-256 When I use PuTTY and specify the private key, after entering the login username it says ssh to 700 and authorized_keys to 600.Īlthough I go to authentication section in WinSCP and specify the private key (as shown in the screenshot) it looks like it still need username and password and doesn't pick it up. The content of authorized_keys looks like as below ssh-rsa AAAAB3NzaC1yc2EAAAABpEVSiiRXi7tOHpkOyFa9w2OLpBep31k9lePCK7RQxsdfs9u11 rdu0XCidRKOY5j4anD1eDaNBj87wqZbsreRe5cFcsakyGUAYXAvqgGApvsep31k9lePCK7RQxlOY5j4anD1eDaNBj8LJO K3SkUN8E0srRBO8YyMT6Y03/F7 AAAAB3NzaC1yc2Q4h2RLGtr12CDKSBVAnFEc JucuF4uF0WY4Sh66MSFI63mCQFu9iYNYwWyT6lUo6sks4WypEVSiiRXi7tOHpkOyFa9w2OLpBzAlTA/VSQwdNTFYUI1vquaufZ9ORzTa6dkbBRo/mLVdevYSRMSDw1BUcinYz/ogdxRvw= I'm using WinSCP to connect and specify the private key in Advanced/Authentication section. Then I try to specify the private key when trying to log in, but apparently it doesn't pick it up and keep asking for the username/password I originally had. ssh/authorized_keys under my user account. I created a public and private key using PuTTYgen and copied the public key to.
0 Comments
Leave a Reply. |