The whole PKI notion, to me kinda always rubbed me the wrong way? Trust, wait, to whom is trust given to implicitly that I do know?!
(Open)SSH's or SILC's TOFU (Trust On First Use) paradigms, seem to avoid a lot of those sorts of pitfalls; though I suppose it creates a little more friction for users? TOFU paradigms also: don't act as a source of profit as the TLS/SSL CA infrastructure did (until Peter Eckersley [RIP] et al created Let's Encrypt to attempt to mitigate that anti-pattern).
It was kinda "hilarious" when some colleagues of mine managed to get a CA to issue a certificate to *. (e.g. https://eprint.iacr.org/2009/111) what could possibly go wrong?! ;)
ティージェーグレェ
npub1k3…zkcx3
2026-10-20 19:02:55 UTC
in reply to nevent1q…t5yv
Author Public Key
npub1k3cx6w0vu5tshrrkfl3ftrd0826e779zgdqy0u8wglylhcy22pks9zkcx3Seen on
wss://relay.momostr.pinkPublished at
2026-10-20 19:02:55 UTCEvent JSON
{
"id": "6d9b45d6bae2970cbaa5d90e1a4a3f75ff035d08c224f8ad103e66eb0a66b7c2",
"pubkey": "b4706d39ece5170b8c764fe2958daf3ab59f78a2434047f0ee47c9fbe08a506d",
"created_at": 1792522975,
"kind": 1,
"tags": [
[
"e",
"2907f70c23243ea4b38eed6df8b0f761f52823eb33b8418a92bc73d353045434",
"",
"root",
"70517381ab3c382310e957f900da12ab82d4ba917641561da3f7fe00c57e52db"
],
[
"proxy",
"https://snac.bsd.cafe/teajaygrey/p/1792522975.787851",
"web"
],
[
"p",
"70517381ab3c382310e957f900da12ab82d4ba917641561da3f7fe00c57e52db"
],
[
"proxy",
"https://snac.bsd.cafe/teajaygrey/p/1792522975.787851",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://snac.bsd.cafe/teajaygrey/p/1792522975.787851",
"pink.momostr"
],
[
"-"
]
],
"content": "The whole PKI notion, to me kinda always rubbed me the wrong way? Trust, wait, to whom is trust given to implicitly that I do know?!\n\n(Open)SSH's or SILC's TOFU (Trust On First Use) paradigms, seem to avoid a lot of those sorts of pitfalls; though I suppose it creates a little more friction for users? TOFU paradigms also: don't act as a source of profit as the TLS/SSL CA infrastructure did (until Peter Eckersley [RIP] et al created Let's Encrypt to attempt to mitigate that anti-pattern).\n\nIt was kinda \"hilarious\" when some colleagues of mine managed to get a CA to issue a certificate to *. (e.g. https://eprint.iacr.org/2009/111) what could possibly go wrong?! ;)",
"sig": "9094029e33928ee6c90af701b04545d6707d6ebb2f697470da236cada4cae32490a997e7649af18a84223df5b8aed37c2cab31dd271622991dc166fad85aec3a"
}