Skip to content

claudiodekker/ungoogled-chromium-macos

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

8 Commits
 
 
 
 
 
 
 
 

Repository files navigation

Signed "ungoogled-chromium" for macOS builds

This repository hosts code-signed and notarized builds of ungoogled-software/ungoogled-chromium-macos.

What's the benefit of these notarized builds?

Your version of macOS will be able to verify that Chromium.app hasn't been tampered with, that to Apple's knowledge the application is safe to run, and that the signer of the application (in this case, me / this repository) has stated as such.

Additionally, it provides applications with the means to trust your Chromium installation. For example, Little Snitch will be able to monitor and perform process identity checks, and 1Password will be able to trust your browser and auto-unlock the extension for you.

Frequently asked questions (FAQs)

Q: Even with this version of Chromium added to 1Password's trusted browsers, the extension won't auto unlock. Why?

That's a somewhat long story, but the fix is pretty straight forward. All you'll have to do is create a 1Password NativeMessagingHost manifest file for Chromium. The easiest way to do so is to simply copy Chrome's:

mkdir -p ~/Library/Application\ Support/Chromium/NativeMessagingHosts/
cp ~/Library/Application\ Support/Google/Chrome/NativeMessagingHosts/com.1password.1password.json ~/Library/Application\ Support/Chromium/NativeMessagingHosts/com.1password.1password.json

Q: I have a different question that isn't listed.

If your question wasn't listed here, please check the README over at the ungoogled-software/ungoogled-chromium-macos repository, the ungoogled-software/ungoogled-chromium repository, or the FAQ's on their Wiki: https://ungoogled-software.github.io/ungoogled-chromium-wiki/faq