It was planned that FTP support would be disabled by default with the release of Chrome 81, and after the release of version 82, all traces of the protocol would be permanently removed from the code. In 2018, the company first announced plans to stop FTP officially, and Google engineers have already begun to implement those plans last summer. Let me remind you that Google developers have been talking about abandoning FTP since 2014, since the protocol is used by very few browser users (0.1-0.2%). The Safari and Firefox developers are just working on fixes.Īnother major change in Chrome 87 was the end of FTP support. Protection is implemented by blocking ports 50, which are used for bypassing firewalls and network address translation (NAT). I must say that Chrome 87 was the first browser protected by NAT Slipstream. To implement such an attack, attackers only need to trick the user to a malicious site. This described by the expert technique allows bypassing firewalls and connect to internal networks, in fact, turning Chrome into a proxy for attackers. Google developers say.Īlso in the new version, was eliminated a vulnerability to the NAT Slipstream attack, about which reported famous information security researcher Samy Kamkar at the end of October this year. Chrome now” launches 25% faster and loads pages 7% faster while using less memory.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |