Step 2: Importing the Private Key into WinSCP ExaVault’s send files option makes a great choice to securely transmit the private key to the end user. If you are generating this key pair for a user other than yourself, you’ll need to get the private key file over to the user so they can import it into WinSCP. You’ll need to be able to find this file later! The public portion of the key will be automatically stored in ExaVault for the user you selected. Some accounts have limits on the number of SSH key pairs that can be stored, so contact support if you need to upgrade your account.īe sure to make note of the download location of the private key file you generate. Once you know the user who should have the SSH key, you can create the key pair directly in ExaVault. If you already have a user that you want to use for the login, skip this step. Set up a new user in your ExaVault account with the appropriate home folder and action permissions. In this blog, we’ll walk you through getting your SSH key imported into WinSCP, a popular FTP client that can be used for manual SFTP connections as well as automated SFTP connections through WinSCP scripting. In either case, ExaVault supports passwordless logins through the use of SSH keys in SFTP connections. Maybe you’re particularly security-minded, or you have an automated script and want to avoid storing the password inside the script. Did you know you can log into your ExaVault account and other servers or applications without transmitting your password? SSH keys are a vital part of this process, allowing you to both secure and automate data transfers.

Supremo 4.10.0.2052 instal the new