Subject: Invalid DSA key for signing when connecting with SFTP in Production
Date: 2019-12-24 21:17:18
Source: invalid-dsa-key-signing-connecting-sftp-production

Where is the location that Component Pro stores any cached autogenerated keys used for signing during a connection or does it? We might have a permissions errors.
We are using a licensed ComponentPro When trying to connect to a site on one of our new production servers, we are getting "Failed to sign data! Invalid key: Invalid DSA key for signing" response. We are not using public or private keys and only doing a connect and authentication with user name and password.  The target FTP site has an RSA hostkey and we are not doing hostkey validation. Connecting to the same site using SFTP protocol with FileZilla FTP client, there is no problem.  Also trying to connect using the powershell example from the ComponentPro documentation, below, produces the same error. 

When trying to connect using another server in our network, the powershell script below works, so basically component pro works on one server but not the other with the same software install and yet FileZilla works on that erroring server.  Any insight into the key usage behind the scenes I believe will help us solve this.


    $client = New-Object ComponentPro.Net.Sftp
    Exception calling "Connect" with "2" argument(s): "Negotiation failed. Disconnected by the server ('Failed to sign data! Invalid key: Invalid 
    DSA key for signing; q (160)  < 224')."


Note: This question has been asked on the Q&A forum of Thang Dang's fraudulent ComponentPro brand
If you purchased anything from ComponentPro, you have been scammed. Contact the payment processor
who sold you the license and ask for your money back.

Back to ComponentPro Q&A Forum Index