for me its no problem to force to save the password, this feature exists and works.

i like the idea of winscp manageing my keys. mainly having a dropdownbox with my current keys with an extra option to "create new keypair" (yes i have multiple keys for different servergroups).
it would be brilliant having winscp doing all the converting to openssh/putty format and uploading the key to the server and adding it to the authorized_key file.

just for comfort :)

To learn when and how passwords are saved to stored session and remembered in memory please read:
https://winscp.net/eng/docs/security_credentials

+1

This request has been added to tracker.

coolvid wrote:

However this takes away one of the great usability features of the software.

Why? If you want to store the password you can, you just need to check the respective box to force WinSCP to do that.

Instead can you not make it so it

(1) Automatically creates a public/private key pair.
(2) Stores the private key for the session
(3) Adds the key to ~/.ssh/authorized_keys on the remote server?

That would be fantastic. It's such a pain to have to do it manually for each server!

You do not have to make new key for each server. You can have one key and use it for all servers.

I know that for very good reasons, you have removed the password save feature:

# When saving session with password, option is given not to store the password.

However this takes away one of the great usability features of the software.

Instead can you not make it so it

(1) Automatically creates a public/private key pair.
(2) Stores the private key for the session
(3) Adds the key to ~/.ssh/authorized_keys on the remote server?

That would be fantastic. It's such a pain to have to do it manually for each server!

Thanks

David.