Chrome 72 Beta Deprecates TLS 1.0/1.1, Steps Towards Deprecating FTP

[phoronix]

Phoronix: Chrome 72 Beta Deprecates TLS 1.0/1.1, Steps Towards Deprecating FTP

Google has rolled out the public beta of the Chrome 72 web browser across all supported platforms. This is a sizable feature release that also packs its share of deprecations...

http://www.phoronix.com/scan.php?pag...-Beta-Released

[tildearrow]

Deprecating FTP? That's not a good thing since I sometimes stumble upon FTP links and it is pretty useful to download them from the browser...

(plus, non-securable is not true... there is FTPS but it is barely, barely adopted)

[dlq84]

Deprecating FTP? That's not a good thing since I sometimes stumble upon FTP links and it is pretty useful to download them from the browser...

(plus, non-securable is not true... there is FTPS but it is barely, barely adopted)

It's a convenience vs security thing. The host needs to adapt and stop using FTP for public file hosting. And they better switch to https too, since eventually http (port 80) will be deprecated too.

[LinAGKar]

It's a convenience vs security thing. The host needs to adapt and stop using FTP for public file hosting. And they better switch to https too, since eventually http (port 80) will be deprecated too.

HTTP can't replace it though, since it doesn't have a concept of files and doesn't support file operations such as dir listing.

[gQuigs]

How did I miss all the browser makers drop tls1.0/1.1 support. I browse with only 1.2+ enabled already... /me ponders if I should make a Firefox addon to make it easier to do...

2020 will have no more Flash and only TLS1.2 and above... nice!

https://www.chromestatus.com/feature/5654791610957824

[TemplarGR]

There is no problem with FTP. Just use an extension if you really need it, or even better, a dedicated FTP application.

[sireangelus]

Why don't we hear about performance improvements anymore?? Did we really hit a wall for it?

[uid313]

Deprecating FTP? That's not a good thing since I sometimes stumble upon FTP links and it is pretty useful to download them from the browser...

(plus, non-securable is not true... there is FTPS but it is barely, barely adopted)

Most users don't care about FTP. If its important to you, just use a dedicated FTP client, such as FileZilla.
Clients can register the ftp:// URI scheme handler so that it launches when you click a hyperlink that points to a FTP resource.

HTTP can't replace it though, since it doesn't have a concept of files and doesn't support file operations such as dir listing.

HTTP have a concept of resources. Resources can be downloadable and can be files.
Most web servers can be configured to list files in a directory.
A REST web application can also give you the directory listing in JSON format.

HTTP verbs

• GET - Downloads a resource (i.e a file).
• POST - Uploads a resource (i.e a file).
• PUT - Updates/modifies/overwrites an existing resource (i.e a file).
• DELETE - Deletes a resource (i.e a file).

[Britoid]

Why don't we hear about performance improvements anymore?? Did we really hit a wall for it?

Any performance improvements would be quickly offset by extra bloat in pages. The web feels slower than 5 years ago.

[cl333r]

And they better switch to https too, since eventually http (port 80) will be deprecated too.

What? When? What port will be used instead? Any links?