Chromium browser sans integration with Google
Project homepage: https://github.com/ungoogled-software/ungoogled-chromium
Description
A lightweight approach to removing Google web service dependency
from the Chromium open-source browser.
Package information
- Ports path
- www/ungoogled-chromium
- Package architecture
- amd64
- Maintainer
- Robert Nagy <robert@openbsd.org>
- Categories
- www, lang/python
- Available flavors
- component, debug, lto
- Only for architectures
- aarch64, amd64, arm, i386, mips64, mips64el, powerpc, powerpc64, riscv64, sparc64
Ports list build and test dependencies as well as runtime dependencies. pkg_add selects those needed for installation.
Direct dependencies
Library
- audio/opus
- devel/pango
- graphics/jpeg
- multimedia/dav1d
- multimedia/openh264
- security/nss
- textproc/icu4c
- textproc/libxslt
- x11/gnome/at-spi2-core
- x11/xkbcommon
- print/cups,-libs
Runtime
- devel/xdg-utils
- devel/desktop-file-utils
- fonts/noto/fonts
- graphics/libexif
- sysutils/libudev-openbsd
- x11/gtk+3
- x11/gtk+4,-guic
- x11/gtk+3,-cups
Build
- archivers/bzip2
- audio/pulseaudio
- devel/gpatch
- devel/gperf
- devel/bison
- devel/esbuild
- devel/llvm/22,-python
- devel/rust-bindgen
- graphics/vulkan-headers
- lang/go
- lang/rust,-rustfmt
- lang/node
- lang/rust
- lang/typescript
- shells/bash
- sysutils/flock
- sysutils/pciutils
- devel/ninja
- x11/py-xcbgen
- x11/qt5/qtbase
- x11/qt6/qtbase
- devel/xdg-utils
- devel/desktop-file-utils
- fonts/noto/fonts
- graphics/libexif
- sysutils/libudev-openbsd
- x11/gtk+3
- x11/gtk+4,-guic
- x11/gtk+3,-cups
- multimedia/aom STEM->=3.14
- multimedia/libvpx
- devel/nasm
- devel/llvm/22
- lang/python/3
- devel/gmake
- archivers/xz STEM->=5.4.0
Test
OpenBSD README
This README contains unresolved ports variables; replace them before using its commands.
+-------------------------------------------------------------------------------
| Running ungoogled-chromium on OpenBSD
+-------------------------------------------------------------------------------
Chromium uses several mitigations on OpenBSD:
- each category of process uses pledge(2) to limit system call access
- each category of process uses unveil(2) to limit filesystem access.
Occasionally, some extensions may violate some pledge(2) specifications.
This will appear in syslog's /var/log/messages as
ungoogled-chromium[<pid>]: pledge "<name>", syscall <n>.
along with the more obvious "Oops" in chromium tabs.
Disabling pledge() or unveil() is not recommended!
THE FOLLOWING INFORMATION IS FOR DEBUG PURPOSES ONLY
- global pledge knob: invoke ungoogled-chromium with --no-sandbox
- specific pledge for specific processes:
${SYSCONFDIR}/ungoogled-chromium/pledge.*
- global unveil knob: invoke ungoogled-chromium with --disable-unveil
- specific unveil for specific processes:
${SYSCONFDIR}/ungoogled-chromium/unveil.*
Specific situations
-------------------
If you need to access files from alternative locations (for example
opening files in /var/www/htdocs directly in ungoogled-chromium), add the paths
to ${SYSCONFDIR}/ungoogled-chromium/unveil.main and merge with changes in files in
/usr/local/share/examples/ungoogled-chromium/ at update time.
webgl and 3d and acceleration support:
- some DRM supported cards are marked as unsupported by ungoogled-chromium
Using --ignore-gpu-blacklist may allow you to test
Interoperability with base window managers:
- some window managers do not have compositing support; for instance, fvwm.
In order to have decent graphic rendering, they should be supplemented by
a compositing manager. For instance, xcompmgr in base.
WebAssembly support:
- some web applications and "not a bot" verification requires support
for WebAssembly, which is disabled by default and can be enabled by
adding ENABLE_WASM=1 to environment variables.