Thanks a lot!

Kind regards,
Dimitri Giwerzew

@dgiwerzew: All correct, no other requirements.

Hello,

I have an additional question regarding using WinSCP .NET assembly in our closed-source commercial application.
If I understood correctly, we need to place in the installation folder a file containing the following copyright information (https://winscp.net/eng/docs/library#license) as well as a link to download the source code: (https://winscp.net/eng/docs/library_install#downloading) like this:

License

The WinSCP .NET Assembly is free library: you can use it, redistribute it and/or modify it under the terms of the Mozilla Public License Version 2.0.
Note that to use the assembly you need to have WinSCP installed. WinSCP uses different license, the GPL.

Downloading
WinSCP .NET assembly is available in a separate package named winscpXXXautomation.zip on WinSCP download page. Follow the .NET assembly/COM library link (https://winscp.net/download/winscp552automation.zip/download)

Furthermore, both the MPL licence for WinSCP .NET assembly (https://www.mozilla.org/MPL/2.0/) and the GPL licence for WinSCP (https://www.gnu.org/licenses/gpl.html) need to be placed there as well.

Is this correct?

Are there any other issues to be considered to use the WinSCP .NET assembly in a closed-source commercial application?

Thank you very much in advance.

Kind regards,
Dimitri Giwerzew

That helps a lot.

Thanks,
Jeff Bowman

Yes, that's correct.

I'd like to use the SFTP component in my closed-source commercial application.

After glancing through the MPL, it seems that I'll need to place a text file in my installation folder. This file should contain WinSCP's copyright information as well as a link to download the source code. Finally, a copy of the current MPL should be placed there as well.

Is my understanding correct regarding this issue?

Thanks,
Jeff Bowman
Fairbanks, Alaska