Hello, when I try to connect via SFTP I get the following error: "Unable to connect to SFTP server: openssh key type: ssh-rsa is not supported"

the file containing the key starts with "-----BEGIN OPENSSH PRIVATE KEY-----", and to test it I used FileZilla, where it works correctly.

Do I need to convert the key to another format or is it a limitation of the DLL? I am currently using the version 7.33.00

Thanks

From what I can tell, the issue is that the server you are connecting to is using an old RSA-1 protocol key that is not supported by the library that we're using (SSH.NET). It's an old standard - the problem is .NET itself doesn't have support for the old protocol any more due to security concerns, so SSH.NET doesn't support it for its keys either.

These are the supported key formats in SSH.NET:

SSH.NET Public Key Authentication

FileZilla apparently still supports the older key format, but that's because it's specifically coded for that while the library is not.

The only way to make this work with the wwSFTP library would be that the server updates to a newer key.

+++ Rick ---

Good morning, thanks for the quick reply. The server manager is available to update the protocols, but asks if it is possible to provide a detailed log. I tried the "cLogFile" property, but it returns the error that it does not exist. thanks

You should be able to pass in a log file, but it doesn't produce a very detailed trace. Unfortunately the underlying library doesn't support a clean way to integrate logging.

As far as the error goes you are getting the raw error message the library which tells you that it can't connect to the key protocol it presents as available. I don't think a log would give you anything more useful in that situation.

I'm taking another look and see if I can make the tracelog work from FoxPro, but so far no luck.

+++ Rick ---

As always, thanks for the reply. The problem is that the manager of the server I connect to tells me that the server protocols are up to date and that I shouldn't have any problems anyway. Could it be a problem with the private key I generated from the client and that I'm passing to "cPrivateKeyFile" at the login call?

Thanks

Honestly I can't say - without knowing what the actual prompt is. From what I can see though it's that the server is requesting the rsa1 auth protocol and that's not available. It's not that the keys are out of date or expired. It's the format is an old and unsupported format (RSA1 key).

+++ Rick ---