botg: I see your back on your soap box, putting your fantasy views, and political agenda ahead of the users and the FTP products. At least you are being a little more honest with us now.
1/ Server admins are not going to change server types or ftp daemons - just to suit you - just to get a "filezilla compliant server".
2/ Its your job to make your client ftp program connect to the world. Even if that world is slightly off.
3/ Your deliberate efforts to make sure your ftp program does not connect - is really bad form.
4/ You choose to read the RFC incorrectly, and deliberately pick an approach that you know does not work everywhere. You should be ashamed of yourself.
I hacked and I changed your existing app config setup, and made it work - everywhere. Its now in TLS 1.2 mode, and connected to an MS FTP server in high security modes. And it was still backward compatible to a 10 year old Apache server. i.e. the perfect setup. If I can do it, then so can YOU!
1/ Server admins are not going to change server types or ftp daemons - just to suit you - just to get a "filezilla compliant server".
2/ Its your job to make your client ftp program connect to the world. Even if that world is slightly off.
3/ Your deliberate efforts to make sure your ftp program does not connect - is really bad form.
4/ You choose to read the RFC incorrectly, and deliberately pick an approach that you know does not work everywhere. You should be ashamed of yourself.
I hacked and I changed your existing app config setup, and made it work - everywhere. Its now in TLS 1.2 mode, and connected to an MS FTP server in high security modes. And it was still backward compatible to a 10 year old Apache server. i.e. the perfect setup. If I can do it, then so can YOU!
