Almost two years have passed since the Google decided to signal the FTP (File Transfer Protocol) as not secure in Chrome. Soon, even that will no longer exist: as of Chrome 82, connections based on this old file transfer protocol will no longer be supported.
It is not a recent decision. Chrome developers have been considering removing FTP support in the browser at least since 2014. The reason is quite obvious: this protocol is very old (it was developed in 1971) and, as such, does not meet current browsers’ security standards for does not have any type of encryption.
In a way, the “boycott” of the protocol started in late 2017, with the launch of Chrome 63. From that version, the browser started to signal FTP connections as not safe, although it did not prevent its use.
In Google Chrome 72, the browser stopped rendering content from FTP. Since then, the browser only allows files from FTP to be downloaded. You can check this out by opening the address ftp://ftp.hp.com/pub/extaccel/landing.jpg on Chrome – until recently, this image was shown by the browser.
The removal of FTP support will be done little by little, starting with Chrome 78. The idea is to get Chrome 82 released (probably in March or April 2020) without any compatibility with the protocol. If the user tries to open an FTP connection in this version or later, the browser will launch a client for this (if it is installed), such as FileZilla.
In Google’s estimates, less than 0.1% of users access FTP connections from Chrome, so the decision should not result in too many complaints. Depending on the application, the adoption of standards such as FTPS (FTP with SSL) may be an alternative.
Other Chromium-based browsers, such as Opera and Vivaldi, are also expected to be affected by the decision. Presumably, FTP support will only continue to exist on them if developers make separate implementations.
With information: gHacks.