![]() # Simple commandline flags for chromium so it does not spoil your privacy. Put this at /etc/profile.d/chromium-ungoogled.sh In this video I show you how to install ungoogled chromium, and some of the benefits of using ungoogled chromium.Download ungoogled chromium herehttps://gith. If you want a universal setting for Ungoogled Chromium, I'm a bit late, but here's a Git repo with settingsįor both Mozilla and Chrom* based browsers: You'll be able to tell that it's ungoogled-chromium by going into the browser hamburger menu and selecting "About", where it will say: "Version xx.xx.x (Official Build, ungoogled-chromium) Ubuntu (64-bit)" The browser will just be called "chromium" in your menu after it is installed, not "ungoogled-chromium. In this video I show you how to install ungoogled chromium, and some of the benefits of using ungoogled chromium. Go to the github page for ungoogled-chromium-debian if you want to read more info: Įcho 'deb /' | sudo tee /etc/apt//home-ungoogled_chromium.list > /dev/nullĬurl -s '' | gpg -dearmor | sudo tee /etc/apt//home-ungoogled_chromium.gpg > /dev/null If you've upgraded to the beta/testing version of Trisquel 10, it will now install and work for you: Right know they have some problem building chromium (with or without any patches) because of the new default cflags used by arch recently, but I think that in a few days everything will be sorted and the package will be available on obs.Ungoogled-chromium recently started hosting a repository that will install the browser on distros based on Ubuntu 20.04. If you want to see which is the last released version you can simply go on aur and see the version there (the PKGBUILD came from their repo).Īs said in the readme of their main repo the binaries are not reproducible, so you can’t trust anyone who publish some binaries, but, in order to solve this problem, they decided to use the OpenSuse Build Service that directly takes the sources from their repo (the PKGBUILD and the other patches) and build the package (so you are sure that is has not been tampered, at least if you trust opensuse). ![]() Their github repo for arch gets new commits quite often (last one is 3 days old at the moment): what are you seeing was some sort of experiment on some ideas on how to provide prebuild binaries I think (the guy that releases them is the contributor from which I get my binaries). Disable features that inhibit control and transparency, and add or modify features that promote them (these changes will almost always require manual activation or enabling).Ībout the first concern I don’t know what to say: right now I use some unofficial binaries (still made by one of the contributor of the project) build for arch and I update them manually whenever, after a manjaro update, the previous version didn’t work anymore because some mismatch in the dynamic libraries (or if a new chromium version is released I, after testing, it still seams to work on my manjaro machine, otherwise i downgrade to the previous version).Remove all uses of pre-made binaries from the source code, and replace them with user-provided alternatives when possible.Remove all code specific to Google web services.Remove all remaining background requests to any web services while building and running the browser.Ungoogled-chromium addresses these issues in the following ways: In addition, Google designed Chromium to be easy and intuitive for users, which means they compromise on transparency and control of internal operations. However, Chromium still has some dependency on Google web services and binaries. Without signing in to a Google Account, Chromium does pretty well in terms of security and privacy. ![]() In scenarios where the objectives conflict, the objective of higher significance should take precedence. However, almost all of these features must be manually activated or enabled.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |