top | item 20711707

Chrome to Deprecate FTP Support

9 points| d3sandoval | 6 years ago |chromestatus.com

10 comments

order

jackfraser|6 years ago

Lame. Is there any real reason to do this? Does the code take a lot of maintenance, aimed as it is against a protocol from 1971? Is there a reason to cut people off from easy interoperability with links on the older parts of the web, many of which surprisingly do still work?

FTP sucks, sure, we get it. No reason to use it now. Still, Google seems to have a mission of deprecating the old Web, from their search results that push that kind of content down, to their browser deprecations of FTP and Flash and Java applets. How is one supposed to even see the old parts of the web anymore?

londons_explore|6 years ago

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 navigate an iframe to FTP://evil_payload@127.0.0.1:3389, allowing me to send a possible exploit to your your machine, bypassing firewalls.

Considering how few people use it, and the risks it still poses to everyone, I can see why they want to get rid of it.

benbristow|6 years ago

If you read the OP it says that their support for FTP is already pretty limited. Doesn't support encrypted FTP (FTPS) or proxies. Kinda goes against the effort they're making to push encrypted connections with HTTP.

They'd have to spend time and effort getting their implementation up to scratch.

Kinda makes sense to scrap the FTP support as there's not much of a user base and leave it to dedicated software like FileZilla/WinSCP/CyberDuck etc. etc.

Piskvorrr|6 years ago

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.

badrabbit|6 years ago

Why of course. To assert dominance! and maintain influence.

It's not about "the old parts",it's more like google's elitist engineers do a stats count and notice only 0.1% kf users use a feature so why spend time maintaining it. Awww,they'll get over it. So what if 0.1% of billions is a million people,not like chrome makes money anyway. What will people do? Boycott google products over ftp support?

Please support google product alternatives. This is how AT&T and Comcast became the way they are. A long slippery slope of not really caring about x% of users.

PauloManrique|6 years ago

This will just break a lot of old sites still linking to FTP resources. Not a bright idea.