The old FTP transport protocol is not guaranteed to support encrypted transmission, so safety and security are not guaranteed, so both Google and Firefox are ready to stop providing support. Google Chrome has also advocated users to transition to a more secure protocol very early, but after all, users are inevitably still using the FTP protocol. However, Google is ready to completely remove the agreement, and will also clean out all the components needed to support this protocol from Google Chrome.
This traditional network protocol is easy to leak information because it does not support encryption, and more and more users are turning to the FTPS/SFTP protocol of the nested encryption layer. There is basically no security in using the FTP protocol on the webpage. It is easy for a hacker to launch a man-in-the-middle attack to hijack and steal user information. Therefore, both Google Chrome and Firefox have gradually cleared the contents of the FTP protocol connection.
From the Google Chrome browser itself, the components of these old protocols have not been moved for a long time, and Google urgently needs to remove all these legacy protocol components. It’s absolutely impossible to improve the security of these legacy components, but the user usage is too low and there is no need to continue to invest. So the easiest and most straightforward way is to clear all components directly from the browser, no longer support the FTP protocol and then focus on other projects. According to Google’s plan, the protocol will be disabled by default in Google Chrome v80, and the support will be completely stopped in the Chrome v82 version.