doesnt work in what way?
#How to remove Chromium from Secureblue ?
tender hatch
and why are you looking to remove chromium in the first place
secureblue expressedly replaces firefox with chromium for security reasons
id recommend you check the readme
along with the default secureblue chromium policies https://github.com/secureblue/secureblue/blob/live/config/files/usr/etc/chromium/policies/managed/hardening.json.readme.md
what error are you getting with rpm-ostree override remove chromium
hallow lake
How to remove Chromium from Secureblue ?
tender hatch
ujust isnt needed
river lynx
It is not killin ublock, it works quite well with manifestv3
river lynx
That is your decision, but the project explicitly states its views on this. Firefox security is notoriously bad especially on linux.
Go right ahead.
Nobody is forcing anybody.
You are free to not use it
shadow cloud
post the result you received in console after typing that command so we know why it didn't work
slate plaza
it's not possible to remove packages layered by an upstream image. In this case secureblue and ublue. This is an rpm-ostree restriction and there's nothing on the secureblue side to help with this.
That aside, this is explicitly out of scope and unsupported
@hallow lake
slate plaza
lol
yeah
there's a ticket against rpm-ostree for it, somewhere
but, even if you could unlayer it, uninstallations on rpm-ostree systems are purely cosmetic for any package
there is no debloating on rpm-ostree systems
every removal increases the image size
@hallow lake
because the base image can't be changed, and removing a package requires storing additional info
tender hatch
i mean realistically if you dont wanna use chromium just dont open it
hallow lake
If I ever want to do stuff completely anonymously, I'd just boot up tails : P
slate plaza
anonimity has nothing to do with secureblue anyhow
hallow lake
Yup
slate plaza
this is a project about security
anyone neglecting to protect themselves against the largest point of attack surface in their system never had security as their top priority to begin with. They are not the target audience of this project
yes this is a copypaste of myself lmao
slate plaza
I'd just like to interject for a moment...
anyways
tldr you can't remove chromium because of an rpm-ostree limitation that may or may not ever be fixed. If you want this functionality, you need to dig up the issue on the rpm-ostree issues page.
In the meantime this is akin to asking GrapheneOS to support removing Vanadium. aka, please don't