Everyone is focusing on the fact that this us C vs rust. The original sudo has issues on its own. Its a large code base that does lots of things and has inherent security vulnerabilities.
Sudo is worth redoing regardless of language.
https://linuxsecurity.com/news/security-vulnerabilities/sudo-flaws-linux-privilege-at-risk
Couldn’t the attacker just drop a dangerous binary into the data volume then?
Linux phone you can buy today and start using:
How would you add new links if its read only?
I’ve been using this which works great.
https://f-droid.org/packages/com.sbv.linkdroid/
Works with my single sign on setup as well which was critical. Creates a nice share target on android so any share button gives the option of sending the link to linkwarden
One thing to consider is that once zfs is setup there really is no significant intervention that is needed. I probably haven’t done anything to my proxmox zfs array in years.
I know its almost a meme to say just learn command line, but unfortunately in this case it will really help you understand what is happening and it also just takes a few commands to setup up once and then never worry about it again.
After the inital setup, the zfs GUI will be pretty much unused.
For commands I don’t use often, i use a note taking software to keep track of commands I used during setup because years go by before I use it again. I find the GUI often changes in that time making it harder to replicate whereas command line is the same and easier to document.
Any idea if gluetun does this by default? A popular setup is setting the network mode on the application docker to the gluetun service and then gluetun itself says it has a killswitch built in. I assume they did that well since its very popular and this is pretty much the main purpose of the container.
The main feature I want is portion scaling. So I can type the number of servings and everything gets multiplied. Is that possible in obsidian via a plugin or with mkdocs?