Chrome to Deprecate FTP Support

Post by OnlyRepliesToBS » Fri, Aug 16, 2019, 6:19 PM UTC

coribuci wrote: post #10

londons_explore wrote: post #4

Earlier quoted context omitted.

The code is old, and hard to secure. It lives in the browser rather than a subprocess, so is unsandboxed. The FTP protocol itself isn't a nice binary protocol - it was designed for humans to type by hand, so has a lot of flexibility, leading to a lot of corner cases in the code. There is also the fact that the flexibility of FTP allows the browser to attack other devices on the local network. For example, I could nav…

There is also the fact that the "modern browser" is no longer a browser but a program which runs remote code with local privileges and sometimes with elevated privileges. The main reason they want to deprecate ftp is the same reason they used for other protocols: it is much easier to control 1 protocol (https) instead of 10 (http, ftp, rss, ntp etc.). Especially when they decide which certificate is trusted in their…

Post by Piskvorrr » Mon, Aug 19, 2019, 12:50 PM UTC

_8j50 wrote: post #9

Piskvorrr wrote: post #6

Earlier quoted context omitted.

I'm honestly surprised that FTP is still supported in web browsers . FTP is as non-web as you can go without resorting to Gopher - plus the protocol is Anfient and Broken (and plaintext [ shudder ]). This shouldn't have been a part of any browser, ever.

There are still sites that have ftp downloads. Sucks to have to install a dedicated client where you could just click and download in the browser.