Let’s encrypt also don’t provide client certificates, or intermediates that allow you to sign them, which really is a shame.
Let’s encrypt also don’t provide client certificates, or intermediates that allow you to sign them, which really is a shame.
It can still prevent vectors of persistency.
That’s patently false.
Yes machinectl is the interface for nspawn
You can have a look at systemd-nspawn and machinectl actually. Sounds like exactly what you’re looking for :)
AppArmor or SELinux, OSSEC, TPM and SecureBoot boot chain.
Dino is nice in GNOME as it’s native Gtk which gets you a nicely integrated and modern look and feel. It’s a little low on feature but fully usable.
*Safer languages
Also both produce single binaries (as opposed to interpreted languages like php, python, js), which is so much easier to deal with for maintenance.
I don’t disagree, but taking notes in Signal gets you syncing automatically which is convenient and something OP asked for 🤷
There’s a note to self feature in Signal
2 years? Try ten!
I mean, it is pretty cool to be able to do long range, encrypted, license free communications. Whether it’s the be all end all, I don’t think so. Reticulum for example seems like a much better thought out protocol. But it’s something, and it works right now. HAM is cool and all, but the lack of encryption makes it pretty useless for day to day usage (and to some people’s SHTF plans).
Instead of a paid subscription for OsmAnd, you can also just install OsmAnd~ from F-Droid and get all the features for free… But it’s fantastic software, consider a donation!
You might want to have a look at https://beets.io
What you want is bind views. You can configure bind to resolve different views for different segments allowing you to have the same (sub) domains to different ips
SSL certs is so easy with let’s encrypt, that really shouldn’t be a blocker.
If you want something easy I think you have your answer with Signal