Gnome-keyring dependency and chromium browsers

Patrick · January 10, 2025, 11:50am

You can follow the history of that here:

This is documented here:

Feel free to experiment with removal of gnome-keyring. This should be easily possible thanks to dummy-dependency, Removal Instructions.

sudo dummy-dependency --yes --purge gnome-keyring

Even if we find a technical solution to do this reliably by default [1], I am not sure we should change chromium default keystore settings. Comments welcome.

[1] We would probably have to solve the stackable wrappers issue.

github.com

Kicksecure/proposals/blob/master/634-stackable-wrappers.md

# Stackable Wrappers (Proposal 634)

- Ticket: https://forums.whonix.org/t/write-draft-for-stackable-wrappers-on-debian-devel/18776
- File: https://github.com/Kicksecure/proposals/blob/master/634-stackable-wrappers.md

# Description

In Debian, there is no such thing as stackable wrappers. It would be desirable to have them.

A wrapper in this context is defined as a minimal script that automatically prepends something in front of a program the user wants to run or appends something, such as default command-line parameters.

Here are some examples of commands to prepend:

* `firejail firefox`
* `torsocks gpg`
* `LD_PRELOAD="$LD_PRELOAD":libeatmydata.so rsync`
* `bindp`, `timeprivacy`, and probably a lot more
* Likely quite a few `dpkg` diversions are used for this purpose

Here are some examples of commands to append:

This file has been truncated. show original