News for hackers. Stuff that matters.
Re:Google Plans to Deprecate FTP URL Support in Chrome by userbinator on Saturday August 17, 2019 @01:17AM (#20722241)
I'm surprised the article claims there are still bugs, because one would think (hope) that a protocol over 30 years old with an implementation over a decade old should've received its last bugfix long ago and become truly stable by now.
Re:Google Plans to Deprecate FTP URL Support in Chrome by bartread on Saturday August 17, 2019 @05:35AM (#20723079)
What? Like OpenSSL:

https://en.wikipedia.org/wiki/Heartbleed

(I mean, I'm not overjoyed at the deprecation of FTP support because I used it just yesterday, but let's at least be honest here. The protocol might be decades old but the implementations aren't necessarily, and if they're being actively maintained there's always the possibility of introducing new bugs.)

Re:Google Plans to Deprecate FTP URL Support in Chrome by userbinator on Saturday August 17, 2019 @02:12PM (#20725377)
It was introduced into the software in 2012

That's not the "stable protocol that's been around for decades" situation that FTP is in.

Re:Google Plans to Deprecate FTP URL Support in Chrome by bartread on Sunday August 18, 2019 @09:39AM (#20730057)
> That's not the "stable protocol that's been around for decades" situation that FTP is in.

That is literally the point I was making when I said, "if they're being actively maintained there's always the possibility of introducing new bugs."

Moreover, just because a library had its last fix a decade (or whatever) ago is no guarantee that unfixed bugs do not lie undiscovered in it.

Re:Google Plans to Deprecate FTP URL Support in Chrome by tylerl on Saturday August 17, 2019 @12:05PM (#20724653)
The protocol is buggy AF. All that crap about sending data over a separate TCP connection, the weird way you have to deal with state and authentication; ftp is an utter shitshow. Just because a protocol is old doesn't mean it's matured to perfection. Telnet is old, so is RCS, and UUCP.

Many protocols evolve not by being replaced by incrementally better point releases, but rather by being supplanted entirely by a better designed alternative.

FTP effectively evolved into HTTP for this use case, and scp/sftp for the authenticated file transfer use case.

Re:Google Plans to Deprecate FTP URL Support in Chrome by a_t48 on Saturday August 17, 2019 @01:47AM (#20722361)
Can you give an example of a piece of software of reasonable complexity (network/file handling, etc) that has solidified like this?
Re:Google Plans to Deprecate FTP URL Support in Chrome by kevin_thibedeau on Saturday August 17, 2019 @02:01AM (#20722403)
TeX
Re:Google Plans to Deprecate FTP URL Support in Chrome by hedora on Saturday August 17, 2019 @11:28AM (#20724503)
Everything in the openbsd base image.
Re:Google Plans to Deprecate FTP URL Support in Chrome by jarfil on Saturday August 17, 2019 @02:33AM (#20722524)
qmail
Re:Google Plans to Deprecate FTP URL Support in Chrome by kibibu on Saturday August 17, 2019 @02:53AM (#20722586)
Sqlite
Re:Google Plans to Deprecate FTP URL Support in Chrome by a_t48 on Saturday August 17, 2019 @03:02AM (#20722617)
The other ones I might give a pass to as I can't find where the update history lives, but this is untrue - https://www.sqlite.org/changes.html
Re:Google Plans to Deprecate FTP URL Support in Chrome by TheSpiceIsLife on Saturday August 17, 2019 @06:27AM (#20723230)
Are you referring to this bit:

and there are other bugs in the implementation which further demotivates the FTP support.

To me that reads as there are bugs in Chrome's implementation of FTP.

Did you take that to mean the author intended to convey the message that the FTP protocol has bugs?