Command line ascp transfer asking for a passphrase after Connect plugin upgrade

Issue

After upgrading the Connect browser plugin to version 3.3.3 or later, you experience different behavior when trying to transfer via the command line in that you are now asked to enter a passphrase.

Below is an example ascp transfer attempt and the resulting passphrase request:

C:\> "C:\Users\Administrator\AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe" -i "C:\Users\Administrator\AppData\Local\Programs\Aspera\Aspera Connect\etc\asperaweb_id_dsa.putty" source_file(s) user@server_IP

Enter passphrase for key 'C:\Users\Administrator\AppData\Local\Programs\Aspera\Aspera Connect\etc\asperaweb_id_dsa.putty':

Environment

  • Product: Connect browser plugin
  • Version: Upgrade from before 3.3 to 3.3 or later
  • Operating System: Windows

 

Solution

This change is due to a new key that was introduced in the newer version of the Connect plugin, and the old one shouldn't be used anymore. So you have to update your command line to:

C:\> "C:\Users\Administrator\AppData\Local\Programs\Aspera\Aspera Connect\bin\ascp.exe" -i "C:\Users\Administrator\AppData\Local\Programs\Aspera\Aspera Connect\etc\asperaweb_id_dsa.openssh" source_file(s) user@server_IP

 

Note: The only necessary change in the command is the asperaweb_id_dsa.putty file to asperaweb_id_dsa.openssh. The rest of the command remain the same as before the upgrade.

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk