The problem is to remove everything make less sense, since a lot of pages will start using it, it would be ‘smarter’ to fix this in protocols itself so that even if a ‘ Malicious’ page could’t abuse it even if they want it. WebRTC is a protocol which is not more or less secure like evrything other protocol. The other gimmicks like WebRTC are not really for securing anything, it’s more gimmick. In FF this plays less a role since you can sync to your own server but not in Chrome. Disable JavaScript dialog boxes from showing when a page closes (Sad to see you go, here is an offer you may be interested in.).Ĭhromium or Chrome are secure, such hardening is only to minimize or elliminate the conections to e.g.Clear HTTP authentication cache on demand from the "more tools" menu.Disable Safe-Browsing, WebRTC, Intranet Redirect Detector.Automatic formatting of the omnibar is disabled (no more stripping).Search provider "no search" added to Omnibox to disable searching.Functionality that is specific to Google domains, Google Host Detector, Google URL Tracker, Google Cloud Messaging and Google Hotwording among others, are disabled.Many web domains referenced by the browser are substituted with qjz9zk.If you dig deeper, you find the following core changes that are made during the ungoogled-chromium creation process: Binaries are build from source, or used when the system provides them. Binaries are stripped from the source tree.Features that communicate with Google or weaken privacy are removed or disabled.It behaves in most regards just like Chromium but with the following main differences: Ungoogled-Chromium is a fork of Chromium that strips many of these bits out of the browser to improve user privacy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |