Maybe not SSL v2-3 why?
SSL is just broken. It's no more secure than plain insecure FTP. Plain FTP still exists in FileZilla Server, and by being honest and explicit about its insecurity, there is no opportunity for users to hind behind a veneer of faux security.
the medical field is bad too typically 10 years behind current.
This is terrible. The medical field in particular should be ahead of the curve. It's the medical field for fucks sake, lives are at stake!
Sure they are less secure
Replace "Less secure" with "completely unsecured", the truth is harsh and brutal. Don't sugarcoat complete lack of security as "less secure".
they will come here complaining spending hours installing uninstalling crying screaming that they just want it to work to hell with security.
They have that option. It's called plain insecure FTP. It's the honest option. Care about security? Update continuously as the threat landscape is evolving. Don't care about security? Use plain insecure FTP. Security is binary, there is no middle ground.
So if it were me taking over Filezilla going from .96 to 1.xxx I would make sure it worked with tls 1.0.
TLS 1.1 came out in 2006. TLS 1.2 came out in 2008. FileZilla Server 1.x came out in 2021. Between 2008 and 2021, what have the developers of these other clients that are stuck on TLS 1.0 been doing all this time? Certainly not improving their software.
They do not have control over 1,000 people that use the FTP so yea very predictable issues and is why many revert back.
What stops these people from just hitting the update button? It's just software. Modern replacement to old junk is just a few mouse clicks away.
Another free program people use is <unimportant detail> to send files via automated FTP. The old version supported tls 1.0 but not the new version and he cant get the new version to work with the new version of filezilla server. Seems programming a working (Free) Ftp server and client is not a cake walk.
That sounds like a skill issue. The libraries are all out there, one just has to use them, it's a piece of cake with the right library. Unless of course they want to implement the TLS and networking libraries themselves, in which case you should tell them to "Git Gud" as the kids say. If their developers have have trouble understanding FTP over TLS on a conceptual level, they are free to contact me, I can explain in excruciating detail, citing RFCs all day long, how it works.