Would it make sense to ship after Chrome to help ensure this does not lead to churn? Also at a time people try to find ways to work from home and share files (spike of usage in Firefox send), potentially breaking ways people have to share files may not be good timing?
On Thu, Mar 19, 2020 at 10:42 AM Frederik Braun <fbr...@mozilla.com> wrote: > > We're doing this for security reasons. FTP is an insecure protocol and > > there are no reasons to prefer it over HTTPS for downloading resources. > > Also, a part of the FTP code is very old, unsafe and hard to maintain > > and we found a lot of security bugs in it in the past. > > I know this used to be (is?) a widely used feature, but I can second > these considerations. It's not right to waste smart network engineering > time on decades old legacy code and it's likely even harder to justify a > rewrite. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
