Notices by 神崎おにいさん✅ (knzk@knzk.me), page 20

@staticsafe I have run another update on the public_key column to source it from the actual keypair, and given them a patch to (temporarily) undo the IP-based fix. In a day or more the accounts should be considered stale, and key caches on other servers should update and fix themselves. To check that it worked, I manually updated key caches on mastodon.social, and was able to successfully communicate with knzk.me

@staticsafe A couple things. If my understanding of the events is correct, the security fix that rate-limits failures in signature verification by source IP backfired on knzk.me because their Puma does not see the real IP address (proxy misconfig). In search of solution, they reset all RSA keys as well, wherein I discovered a bug in the tootctl command that does that, so the accounts were advertising one public key, while signing with another.

Helping bring knzk.me back to life...

i want to thank @eugen, @y, @Knzk and @knzkdev for all their hard work, either in maintaining/running this place or in eugen's case for helping figure out the problem of federation. teamwork brought this place back. i'm grateful!

THE WHOLE GANG IS HERE
(pwease don't hellthread these people. they are too precious for that)

@Knzk @cambrian_era @amic @anna @killeveryhetero @sophia @socialskeleton @cocoron

FOLKS WE MUST WISH JAPANESE ADMIN @y A HAPPY BIRTHDAY!! #knzk :hacker_k: :hacker_n: :hacker_z: :hacker_k: :hacker_g: :hacker_a: :hacker_n: :hacker_g:

1　年　ぶ　り

KNZK will live on forever