Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: Log: unable to use private key

It does not matter how you run PuTTYgen, as long as you use the latest version.
rkylegreen

Re: Log: unable to use private key

Martin, thanks for the reply.

In PuTTYgen, I think I accepted the defaults, assuming that would be best. I will regenerate the keys, and pay more attention this time.

Last time I ran PuTTYgen separately. Is it suggested that I do it from within WinSCP instead?

Thanks,
Kyle
martin

Re: Log: unable to use private key

Well, then the key is probably SSH-1. Haven't you selected "SSH-1 (RSA)" key type in PuTTYgen, when generating the key? Do not do that. No modern SSH client nor server support SSH-1 anymore.
rkylegreen

Log: unable to use private key

I included about 50 lines of the log below.

Things seemed to be going well with the connection until these lines in the log:
. 2024-09-07 20:01:12.401 Reading key file "C:\Users\bob\.ssh\FirstPrivate.ppk"
. 2024-09-07 20:01:12.401 Unable to use this key file (SSH-1 private key)
! 2024-09-07 20:01:12.401 Unable to use key file "C:\Users\bob\.ssh\FirstPrivate.ppk" (SSH-1 private key)

The public key is in c:\ProgramData\ssh\administrators_authorized_keys, on a single line, and appears to be in good shape. The user logging in is in the Administrators Group. sshd_config specifies the above named file.

There was a warning about SSH-1, but I used PuTTYgen to create them, so I thought they would be up to par.

Is that the reason for the failure, or should I be looking at something else. Thanks!
. 2024-09-07 20:01:11.977 Using SSH protocol version 2
. 2024-09-07 20:01:11.977 Have a known host key of type ssh-ed25519
. 2024-09-07 20:01:12.065 Detected network event
. 2024-09-07 20:01:12.065 Enumerating network events for socket 2044
. 2024-09-07 20:01:12.065 Enumerated 1 network events making 1 cumulative events for socket 2044
. 2024-09-07 20:01:12.065 Handling network read event on socket 2044 with error 0
. 2024-09-07 20:01:12.065 Waiting for the server to continue with the initialization
. 2024-09-07 20:01:12.065 Looking for incoming data
. 2024-09-07 20:01:12.065 Looking for network events
. 2024-09-07 20:01:12.066 Doing ECDH key exchange with curve Curve25519, using hash SHA-256
. 2024-09-07 20:01:12.217 Detected network event
. 2024-09-07 20:01:12.217 Enumerating network events for socket 2044
. 2024-09-07 20:01:12.217 Enumerated 1 network events making 1 cumulative events for socket 2044
. 2024-09-07 20:01:12.217 Handling network read event on socket 2044 with error 0
. 2024-09-07 20:01:12.217 Waiting for the server to continue with the initialization
. 2024-09-07 20:01:12.217 Looking for incoming data
. 2024-09-07 20:01:12.217 Looking for network events
. 2024-09-07 20:01:12.256 Server also has ecdsa-sha2-nistp256/rsa-sha2-512/rsa-sha2-256/ssh-rsa host keys, but we don't know any of them
. 2024-09-07 20:01:12.256 Host key fingerprint is:
. 2024-09-07 20:01:12.256 ssh-ed25519 255 SHA256:1jQcp2N9JZLQGQ/2+dR8Vt/vhpO6YAbnAFYoGpwREu0
. 2024-09-07 20:01:12.256 Verifying host key xxx
. 2024-09-07 20:01:12.314 Host key matches cached key
. 2024-09-07 20:01:12.315 Initialised AES-256 SDCTR (AES-NI accelerated) [aes256-ctr] outbound encryption
. 2024-09-07 20:01:12.315 Initialised HMAC-SHA-256 outbound MAC algorithm
. 2024-09-07 20:01:12.315 Initialised AES-256 SDCTR (AES-NI accelerated) [aes256-ctr] inbound encryption
. 2024-09-07 20:01:12.315 Initialised HMAC-SHA-256 inbound MAC algorithm
. 2024-09-07 20:01:12.401 Detected network event
. 2024-09-07 20:01:12.401 Enumerating network events for socket 2044
. 2024-09-07 20:01:12.401 Enumerated 1 network events making 1 cumulative events for socket 2044
. 2024-09-07 20:01:12.401 Handling network read event on socket 2044 with error 0
. 2024-09-07 20:01:12.401 Waiting for the server to continue with the initialization
. 2024-09-07 20:01:12.401 Looking for incoming data
. 2024-09-07 20:01:12.401 Looking for network events
. 2024-09-07 20:01:12.401 Reading key file "C:\Users\bob\.ssh\FirstPrivate.ppk"
. 2024-09-07 20:01:12.401 Unable to use this key file (SSH-1 private key)
! 2024-09-07 20:01:12.401 Unable to use key file "C:\Users\bob\.ssh\FirstPrivate.ppk" (SSH-1 private key)
! 2024-09-07 20:01:12.442 Using username "bob".
. 2024-09-07 20:01:12.563 Detected network event
. 2024-09-07 20:01:12.563 Enumerating network events for socket 2044
. 2024-09-07 20:01:12.563 Enumerated 1 network events making 1 cumulative events for socket 2044
. 2024-09-07 20:01:12.563 Handling network read event on socket 2044 with error 0
. 2024-09-07 20:01:12.563 Waiting for the server to continue with the initialization
. 2024-09-07 20:01:12.563 Looking for incoming data
. 2024-09-07 20:01:12.563 Looking for network events
. 2024-09-07 20:01:12.564 Server offered these authentication methods: publickey,keyboard-interactive
. 2024-09-07 20:01:12.564 Attempting keyboard-interactive authentication
. 2024-09-07 20:01:12.656 Detected network event
. 2024-09-07 20:01:12.656 Enumerating network events for socket 2044
. 2024-09-07 20:01:12.656 Enumerated 1 network events making 1 cumulative events for socket 2044
. 2024-09-07 20:01:12.656 Handling network read event on socket 2044 with error 0
. 2024-09-07 20:01:12.656 Waiting for the server to continue with the initialization
. 2024-09-07 20:01:12.656 Looking for incoming data
. 2024-09-07 20:01:12.656 Looking for network events
. 2024-09-07 20:01:12.656 Server refused keyboard-interactive authentication
. 2024-09-07 20:01:12.656 Server offered these authentication methods: publickey,keyboard-interactive
. 2024-09-07 20:01:12.657 No supported authentication methods available (server sent: publickey,keyboard-interactive)