there is even an FTP indexer:
https://www.securitynewspaper.com/2018/12/10/list-of-all-ope...
61–70 of 86 posts
there is even an FTP indexer:
https://www.securitynewspaper.com/2018/12/10/list-of-all-ope...
Insecure? Bullshit. They should remove http then. I'd respect them if they just said they're lazy and don't want to support the ftp protocol.
> They should remove http then. They're working on it. It has and will continue to be deprecated with ever increasing security warnings. But the reason why FTP got pulled and HTTP hasn't is simply usage. The FTP client in browsers is terrible, and anyone using FTP professionally is using a better client (e.g. multiple connection modes, resume downloads, concurrent streams, etc) or has already migrated to FTPS or SFTP…
Earlier quoted context omitted.
Perhaps they should take the opportunity to rewrite it in Rust.
If I'm reading the telemetry correctly ( https://mzl.la/3bq5oFZ ), there are ~6k people who used FTP to download a file in the past week or so. That's not enough users to really justify spending manpower rewriting it.
Earlier quoted context omitted.
> They should remove http then. They're working on it. It has and will continue to be deprecated with ever increasing security warnings. But the reason why FTP got pulled and HTTP hasn't is simply usage. The FTP client in browsers is terrible, and anyone using FTP professionally is using a better client (e.g. multiple connection modes, resume downloads, concurrent streams, etc) or has already migrated to FTPS or SFTP…
So why aren't you arguing that firefox support migration to ftps or sftp?
> The FTP client in browsers is terrible, and anyone using FTP professionally is using a better client (e.g. multiple connection modes, resume downloads, concurrent streams, etc)
That would be just as true for SFTP or FTPS. Those mitigate the security problems, but don't address the fact that FTP-like protocols would continue to be a second class citizen in browsers and better handled by bespoke clients.
Other than a part time dev and some testing, it's hard to see the costs of supporting ftp.
It's a string of decision-making like this that has made FF drop off the list of "supported" browsers in many organizations and may lead to a 2 engine Internet. This is bad for everyone, IMO.
Mozilla board: Look at your browser share: you need to replace the management team immediately - we need FF.
I can see many tech ppl switching over to a chromium browser because they might possibly use ftp in the future and just want to install one browser. It's those ppl that install (or even know about) FF, generally. Other than a part time dev and some testing, it's hard to see the costs of supporting ftp. It's a string of decision-making like this that has made FF drop off the list of "supported" browsers in many organi…
Plus Mozilla isn’t an organisation the size of Google. They have to prioritise what they’re going to support and it makes total sense to ditch FTP support. I’m a professional web developer and I’d never choose which browser I use based on whether it supports FTP. I barely ever use it, and when I do I just use FileZilla or something similar that makes much more sense for FTP.
Earlier quoted context omitted.
Well it reeks a bit because from the article "Mozilla could have opted for implementing support for secure FTP in Firefox; a bug was filed 19 years ago to introduce support for SFTP in Firefox but nothing ever came out of it."
Never happened because there was no use case for it. FTP made some sense to have in a browser because it supported unauthenticated downloads. SFTP, as a protocol which runs over SSH, basically requires authentication. (You could conceivably set up an SSH server to allow authentication against a "guest" user, but that gives security folks the heebie-jeebies.) So it doesn't really make sense to link to an SFTP resource…
Earlier quoted context omitted.
If I'm reading the telemetry correctly ( https://mzl.la/3bq5oFZ ), there are ~6k people who used FTP to download a file in the past week or so. That's not enough users to really justify spending manpower rewriting it.
you should never trust telemetry or analytics to be unspoofed.
Earlier quoted context omitted.
> They should remove http then. They're working on it. It has and will continue to be deprecated with ever increasing security warnings. But the reason why FTP got pulled and HTTP hasn't is simply usage. The FTP client in browsers is terrible, and anyone using FTP professionally is using a better client (e.g. multiple connection modes, resume downloads, concurrent streams, etc) or has already migrated to FTPS or SFTP…
You probably don't realize many links you click are ftp links that will now be broken for you.
I can see many tech ppl switching over to a chromium browser because they might possibly use ftp in the future and just want to install one browser. It's those ppl that install (or even know about) FF, generally. Other than a part time dev and some testing, it's hard to see the costs of supporting ftp. It's a string of decision-making like this that has made FF drop off the list of "supported" browsers in many organi…
Google doesn't need their browser to make money, and Google advertises their browser in ways that Mozilla can't match. It's surprising that Mozilla can even be half-healthy.