@d71107 yeah, unfortunate but I’ve been debating running my own Matrix server; not sure which Mastodon server to switch to though.
It is proven! I am kisom on Keybase: https://keybase.io/kisom/sigchain#e6691e1c2b069abac7879e9091bc500e75042576d27893e0c2c84d1dbd7385e00f
I've started wroting a portable version of OpenBSD's signify(1): https://github.com/kisom/psignify
@stephenjahl now if only their server wasn’t closed source.
@stephenjahl or keybase but I guess that’s more work (also TIL about Tutanota)
@stephenjahl obviously time for a key party
@stephenjahl @qbit I’ll have to find time to fix... after I fix the tyrfingr server...
@stephenjahl Hmm, I just set up tt-rss but maybe I should check it out, reduce the amount of php in my life...
@vaelen what happened this time?
Thread:
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?
@fribbledom It was really heartening to see Debian making an effort towards this.
The problem is intermediates are often signed for ~3 years - just long enough for a lot of the engineers who set them up to have left or to be mostly forgotten because they just work. Three years comes faster than you think...
The core problem is people mostly only think about roots and leaves; it’s not until you get bit by this that it starts to become institutional memory.