We need to talk about packaging, signatures, checksums and reproducible builds:
On your system you have a keyring of packagers' GPG keys that you inherently trust.
Releases get signed with a key, which verifies the packager as the author, and supposedly lets you and your system trust their contents.
But do you really trust your packagers? How could you? Do you know them personally and monitor their packaging work?
Would you even know if they release a package with malicious content?
I remember running into this at a past employer where TLS certs were core to the business. It happened on a New Year’s Day, and I spent a lot of that holiday trying to fix it.
Have a listen! https://nullstate.bandcamp.com/album/misguided-ventures
“The next-generation DNS”, a hosted, private DNS resolver with DoT and DoH support and blocklists. https://www.nextdns.io
I built my own S/MMS microblogging site and decided to write up a little about it: https://ai6ua.net/blog/2019/05/10/hello-nomad/
I’ve been giving riot a go and... it’s barely usable. Constant problems with undecryptable messages, the key verification process is cumbersome. There should be an option to TOFU or verify all. Signing out caused my iPad to lose all its keys and I had to approve from a different device. I don’t know how this is supposed to be an acceptable alternative from a usability standpoint to other offerings.
@stephenjahl Nice header photo, by the way :)
@stephenjahl that was fast