I'd like to use it, but I'm hesitant to use anything that isn't a reviewed and approved package in my Linux distribution. Even if the chance is 1% that a program I download has malware or security problems that even the author doesn't know about (eg., due to libraries used), odds are that my system's going to be compromised if I run 50 such programs. This extends to browser add-ons, bookmarklets, and extensions too.

How do other people handle this dilemma?

Even solution I can think of involves are a great amount of extra work.

▲

nobody42 an hour ago | parent | next [-]

And it's a proper way to use computer nowadays.

Apart from high-overhead solutions like VMs and containers, there are seamless and maintenance-free solutions (after the initial setup):

- systemd service hardening [0] [1]

pretty powerful, but it's a blacklist approach - whack-a-mole

- AppArmor [2]

Whitelist, proactive approach. Contrary to SElinux, it's not a programming language, and could be grasped pretty quickly. I made a tool to easily convert AA logs into usable rules. [3]

[0] https://github.com/alegrey91/systemd-service-hardening

[1] https://github.com/desbma/shh

[2] https://presentations.nordisch.org/apparmor/

[3] https://github.com/nobody43/apparmor-suggest

▲

invalidator 3 hours ago | parent | prev | next [-]

I think the best answer lies somewhere in compartmentalization and fine-grained permissions. In this case: run it in some kind of secure container which has access to read browser history, and write to its database, but definitely does not have network access.

Unfortunately there's no one-size-fits-all solution for this yet, but there are a lot of groups attacking it from different angles: Qubes, GrapheneOS, Firejail, Bubblewrap, Android/iOS app permissions, Landlock, App Sandbox, etc.

	▲	EvanAnderson 24 minutes ago \| parent [-]
		> ...run it in some kind of secure container which has access to read browser history, and write to its database, but definitely does not have network access. We should be doing this with all software, regardless of provenance, anyway. Least privilege applies to servers just as much as it does to users. Even if the software isn't untrustworthy you can be it has vulnerabilities. My first go-to is network segmentation because I spend most of my time doing networking work. For every vendor who has shit-talked me to Customers ("Wah, wah! Your networking vendor is making this so much harder because they want us to enumerate our traffic!") I have concrete examples I can cite when attacks were stopped by network segmentation (preventing shellcode from downloading a payload, preventing C2 communication, firing off alerts when unexpected network traffic starts coming out of a host, etc). Beyond network segmentation, I am very suspicious of software that needs to run as a privileged user. So many attacks get easier when privilege escalation in the host OS is already done for you.

▲

BrokenCogs 6 hours ago | parent | prev | next [-]

Clone the repo and ask your llm of choice to audit any security risks

▲

edoceo 6 hours ago | parent | next [-]

After that I run them in containers, no network access, ro filesystem.

▲

computator 6 hours ago | parent | prev | next [-]

And then build from source. And make sure it doesn't auto-update so no new malware gets in. This is my idea of a lot of extra work.

	▲	itsdesmond 5 hours ago \| parent \| next [-]
		Why even ask the question?
	▲	applfanboysbgon 6 hours ago \| parent \| prev [-]
		Building from source is nowadays writing one sentence in a chat box. Your idea of extra work is either unbelievably lazy or perhaps outdated by a few years.

▲

Eduard 6 hours ago | parent | prev [-]

good luck auditing all transitive dependencies

▲

Zephyrix 4 hours ago | parent | prev [-]

Distro maintainers aren’t infallible either. At the end of the day it’s up to you to decide where and how much trust you place and do your due diligence from there.

One thing that can be helpful when reasoning about things like this is figuring out what your actual threat model is. What does system compromise look like to you? Data exfiltration, arbitrary code execution, something else?