![]() This helped to prevent us poor distro packagers from being billed for Cloud API usage in case our browser packages gained popularity.Īnd then, early 2021, some Google white-collar people decided they had enough of these freeloaders. So on top of providing us access to these Google APIs (in the case of Open Source Distro Chromium packagers) the Chromium team also substantially increased the non-billed monthly API consumption by the users of our distros’ Chromium browsers. If you offer a product that calls upon Google’s Web Services there is a monetary cost involved once the number of your users’ connections exceeds the monthly upper limit for free usage. In order to boost the development of Chromium-based (embedded) browser products, Google made deals with 3rd parties as far back as 2013 (from what I could find) and spiced the API keys of these 3rd parties with access to crucial Google Webservices providing features that would draw users to these products. ![]() This Chrome Sync capability in Chromium based browsers allows you to login to Google’s Sync cloud servers and save your passwords, browsing history and bookmarks/favorites to your personal encrypted cloud vault inside Google’s infrastructure.Įxtremely convenient for people who access the Internet using multiple devices (like me: Chrome on a few Windows desktops, Chromium on several Slackware desktops and laptop and Chrome Mobile on my Android smartphone) and who want a unified user experience in Chrome/chromium across all these platforms. ![]() The most prominent feature which will be blocked after March 15th is the “Chrome Sync”. ![]() The safe browsing feature identifies unsafe websites across the Internet and notifies browser users about the potential harm such websites can cause. The most important service that remains open is “safe browsing”. Meaning, every Chromium based product not officially distributed by Google will be limited to the use of only a few public Google Chrome web services. On March 15th 2021, Google is going to block non-Google chromium-based browsers from accessing certain “private Google Chrome web services” by unilaterally revoking agreements made with 3rd parties in the past. … Aka the future of Chromium based (embedded) browsers Posted in Slackware, Software | 11 Comments | How to ‘un-google’ your Chromium browser experience If you still want Chrome Sync to work with Chromium, I just want to point you to “/etc/chromium/nf” in my future packages and get inspired by its content. That will leave the Safe Browsing functional, but it removes the Chrome Sync and other features. I noticed that Chromium still works as before, even now after the 15 March deadline has passed, but future builds of my package will only contain my API key. The update takes care of that.Īlso, this was the last package which i compiled for Chromium that contains my Google API Key as well as the OAuth client/secret credentials. That is not needed for chromium-ungoogled itself, but I was alerted to the fact that Spotify specifically looks for ‘libwidevinecdm.so’ in the toplevel Chromium library directory. The change to the package is small: it adds a compatibility symlink. The ‘real’ Chromium does not need or use it, since Chromium downloads this CDM library automatically for you. The Widevine plugin package for which I provided an update, is meant for chromium-ungoogled only. I assume that the patch will end up in the Chromium source code after it passes the internal review process. And the fix took a while to actually get implemented, but in the end it all worked out. Google is no longer offering 32-bit binaries which means, issues like these are not likely to be caught in their own tests, but they are listening to the packagers who do build 32-bit binaries. In that same chromium-distro-packagers group that is the home of the discussion about Google’s decision to cripple 3rd-party Chromium browsers, I had asked the Chromium team to address the crash Slackware users are experiencing. Since I had to build packages anyway, I took the opportunity to apply a patch that fixes the crashes on 32-bit systems with glibc-2.33 installed (i.e. I made chromium-ungoogled also available for Slackware 14.2, I hope that makes some people happy. You are urged to update your installation of Chromium (-ungoogled) ASAP. 90 release addresses several critical vulnerabilities (it’s the third release in the 89 series in rapid succession actually, to fix critical bugs) but in particular it plugs a zero-day exploit that exists in the wild: CVE-2021-21193. I have updated the ‘ chromium‘, ‘ chromium-ungoogled‘ and ‘ chromium-widevine-plugin‘ packages in my repository.įor Chromium (-ungoogled) these are security updates.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |