martin wrote:

SFTP (SSH) does not use certificates. Maybe you mean FTPS? In that case you need to set SessionOptions.TlsHostCertificateFingerprint to accept a non-trusted certificate.
https://winscp.net/eng/docs/library_sessionoptions#tlshostcertificatefingerprint

My mistake then. I'm not familiar enough yet with either one to have known this.

So now I know ;-)

Thanks,
Jeff Bowman
Fairbanks, Alaska

SFTP (SSH) does not use certificates. Maybe you mean FTPS? In that case you need to set SessionOptions.TlsHostCertificateFingerprint to accept a non-trusted certificate.
https://winscp.net/eng/docs/library_sessionoptions#tlshostcertificatefingerprint

Update: The server admin has provided a trusted certificate, so this is no longer an issue.

However it would be nice to know, just out of curiosity.

Thanks,
Jeff Bowman
Fairbanks, Alaska

I'm considering using the .NET assembly on a project for a customer. Unfortunately, he's in a bit of a fix.

He doesn't have control over the server he's connecting to and a non-trusted certificate will be in place for the next several weeks. He also is unable to get the Root CA in the meantime.

How will WinSCP's SFTP component react to this? Will a connection even be possible?

Thanks,
Jeff Bowman