Please add support of sftp and scp protocols in the "System.Net" Namspace. Since FTP isn't a reliable protocol any more, it is time to support more secure and widly supported protocols for .net core.
.NET Core avoids implementing authentication/encryption but defers that to the OS.
For example: SslStream uses OpenSSL on Linux.
For SFTP, SCP this would mean an extra dependency (for example, on libssh).
A 3rd party package is probably your best option: https://www.nuget.org/packages?q=ssh.
cc @bartonjs
Okay, I got the point.
Most of the free available options aren't maintained well. like SSH.NET
So, it seems cryptography doesn't seems an issue any more. https://github.com/dotnet/corefx/blob/master/Documentation/architecture/cross-platform-cryptography.md
So, it seems cryptography doesn't seems an issue any more.
Some concrete issues I'm aware of:
Most of the free available options aren't maintained well. like SSH.NET
SSH.NET works fine for most use-cases. If you have specific issues, report them in the GitHub project: https://github.com/sshnet/SSH.NET.
Triage: Let's see more about interest from community (upvotes).
Note: This may be better suited for external library, not necessarily have it in the platform itself.
@tmds +1 for native SSH support in .NET Core. SSH.NET is effectively broken on macOS Catalina due to https://github.com/sshnet/SSH.NET/issues/355
@MattMcL4475 I'll be fixing that issue some time this week. I know it's long overdue.
Maintained list of all known 3rd party SFTP client libraries for .NET (both free and commercial) is here: https://www.sftp.net/client-libraries
@MattMcL4475 In case you didn't see the announcement, the issue you mentioned (https://github.com/sshnet/SSH.NET/issues/355) is fixed in version 2020.0.0-beta1 of SSH.NET.
Is there a reason to keep this open now? Is there an unmet need that can only reasonably be met in the platform itself?
This is right, there is no reason to keep this issue open.
Thanks @chrgraefe
Most helpful comment
@MattMcL4475 In case you didn't see the announcement, the issue you mentioned (https://github.com/sshnet/SSH.NET/issues/355) is fixed in version 2020.0.0-beta1 of SSH.NET.