Open brianmego opened 7 years ago
Swish hasn't been updated by the author since June 2013 (http://www.swish-sftp.org). It can be installed under Windows 10 but it displays an error message "Unable to exchange encryption keys: LIBSSH2_ERROR_KEX_FAILURE. I think it's because the libssh2.dll file installed by Swish is too old.
According https://sourceforge.net/projects/swish/, someonelse has also a problem to run Swish under Windows 10:
sean729 Posted 08/25/2018 I couldn't get swish v0.8.2 working on Windows 10 Home (64 bit), so instead went with the commercial/opensource product called WinFSP (Windows File System Proxy) from www.secfs.net/winfsp -- which also supports mapping as a drive for NFS and SSH. BTW, those that need documentation should use the wayback machine.
Maybe we should reject this request?
Does the issue only occur on Windows 10 or other operating systems that Chocolatey supports?
No idea. But, a lot of changes have been applied on the SSL protocol since 2013 (encryption, cyphers etc...). For me, it's a bad idea in term of security to provide a such unmaintened package. And no idea if it can runs on other windows versions.
Le sam. 20 avr. 2019 à 17:58, Paul Broadwith notifications@github.com a écrit :
Does the issue only occur on Windows 10 or other operating systems that Chocolatey supports?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/chocolatey/chocolatey-package-requests/issues/192#issuecomment-485138298, or mute the thread https://github.com/notifications/unsubscribe-auth/AABQJ23V7V6VRLOBVUY6XUDPRM4T7ANCNFSM4EBHGDCQ .
Chocolatey supports other operating systems. If it runs on them then there is no reason it should not be a package. I would expect the maintainer to identify that it won't run on Windows 10 or implement a workaround if there is one.
If there is no security issues reported then again there is no reason for it not to be a package.
Whether it's a good idea or bad to use an older / unmaintained library that has no reported issues is a user decision not a Chocolatey repository one.
Do not do enough Windows development to justify being the main maintainer of this package any longer.
Source for the existing package exists here: https://github.com/brianmego/Chocolatey