Ungoogled chromium flatpak install#
Ungoogled chromium flatpak update#
Ungoogled chromium flatpak manual#
Ungoogled chromium flatpak code#
Ungoogled chromium flatpak download#

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).Remove all uses of pre-made binaries from the source code, and replace them with user-provided alternatives when possible.

Ungoogled chromium flatpak code#

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.

ungoogled-chromium features tweaks to enhance privacy, control, and transparency.

Unlike other Chromium forks that have their own visions of a web browser, ungoogled-chromium is essentially a drop-in replacement for Chromium.

ungoogled-chromium retains the default Chromium experience as closely as possible.

ungoogled-chromium is Google Chromium, sans dependency on Google web services.

In descending order of significance (i.e. Help is welcome! See the docs/contributing.md document for more information.

Ungoogled chromium flatpak update#

Update comments referencing buildkit to something elseĪ lightweight approach to removing Google web service dependency Replace scheme relative URLs with https URLs ( #2171 )Īdd 'goo.gle' to domain regex, include typescript ( #2073 )

Ungoogled chromium flatpak download#

Utils/downloads.py: Support axel and curl, and download resumptionĬirrus CI: Add pytest-cov to requirements.txtĪdd timestamp manipulation to domain substitution Make -cache argument to domain_substitution.py optionalĭevutils/validate_patches.py: Add -dry-run to verbose error For any fellow users of an Arch-based distribution, I will append a note of caution that building the Arch User Repository version of Ungoogled Chromium is a RAM-intensive task.Split the referrer-directive flag into multiple feature flags For those who are interested in trying the Google-free version of Chromium, it is available for Windows, Mac, and Linux (some distributions have specific packages, others can use the Flatpak version). I conclude by offering my gratitude to Eloston and all the contributers to the Ungoogled Chromium browser for the hard work they put in to maintain a valuable project. I have no need to jump through the hoops since I have a suitable backup authentication method for Google that works in Ungoogled Chromium and all browsers (and because this issue only affects Google), but it was an interesting discovery nevertheless. However, as the user opined (and I agree): “Unless this is someone only means of authenticating with Google, I would rank this as a low priority issue.” In order to use two-factor authentication on Ungoogled Chromium, an additional extension is needed.Īccording to an April 2020 GitHub exchange between a user and the maintainer of Ungoogled Chromium ( Eloston), the additional extension method may not always work. After installation you might need to restart your computer to make it work.Īs I suspected, Google handles FIDO two-factor authentication different than other services that allow it do.

Ungoogled chromium flatpak install#

You’ll need to install this extension to make this function. Google sign in uses a specific extension to access the security key’s information. The following is quoted from the Ungoogled Chromium Wiki: Out of curiosity, I decided to check its GitHub repository page to see if my question would be answered.īecause Ungoogled Chromium is well-documented, it did not take me long to find the answer to my question. Ungoogled Chromium is a fully open source web browser with its source code published on GitHub. I suspected that it had something to do with the ungoogled aspect of Ungoogled Chromium. This was ultimately no problem – I have a second second-factor authentication method enabled (TOTP with Aegis Authenticator), but I was curious why my security keys did not work for logging into Google from Ungoogled Chromium.

When I tried to log into my Google account, I received an error message informing me that there was an issue with my preferred second-factor authentication method. I redacted my NLJ Google email (lest anyone think the issue was my forgetting to type an email) and I added a yellow square around the pertinent part of the image. Photo of my sign-in to Google on the Ungoogled Chromium browser.