We took care of it: now the Browsing Security database of dangerous domains is stored locally on your computer, and the application contacts the server from time to time to update it. Secondly, this delay carried some danger in itself: this time could be enough for a malicious code to be executed. That method had a couple of imperfections: firstly, sending the request took up some time. Previously, every time you visited a website, Browsing Security would send requests to a server containing a list of malicious and phishing domains to check whether the website could be dangerous. What we've changed: now, Browsing Security uses the protocol Safe Browsing API v2 instead of Lookup API. It functions in a new way now – the Internet is safer than ever before! You might have seen a nice looking banner caringly stating "AdGuard has blocked access to this page": that's what Browsing Security does. Browsing Security functions in a new wayīrowsing Security is a module that blocks requests to malicious and phishing websites. Yes, there were fewer tasks in this version, but we did a good job on improving everything: Browsing Security, network drivers, CoreLibs and DNSLibs, other minor features, and – hopefully – your user experience. We once again reviewed GitHub repo – and realized that we'd been working for almost six months on version 7.7. Feeling Christmas yet? We wanted to boost the festive spirit – and brought you a small gift: AdGuard v7.8 for Windows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |