In reply to
Filippo Valsorda
@filippo@abyssdomain.expert
@FiloSottile elsewhere / Cryptogopher / Go crypto maintainer / Professional Open Source maintainer / RC F'13, F2'17 https:// mkcert.dev / https:// age-encryption.org / https:// filippo.io/newsletter 🕳️ “Gaze not into the abyss, lest you become recognized as an abyss domain expert, and they expect you keep gazing into the damn thing.” — @ nickm
abyssdomain.expert
Filippo Valsorda
@filippo@abyssdomain.expert
@FiloSottile elsewhere / Cryptogopher / Go crypto maintainer / Professional Open Source maintainer / RC F'13, F2'17 https:// mkcert.dev / https:// age-encryption.org / https:// filippo.io/newsletter 🕳️ “Gaze not into the abyss, lest you become recognized as an abyss domain expert, and they expect you keep gazing into the damn thing.” — @ nickm
abyssdomain.expert
@filippo@abyssdomain.expert
·
Apr 07, 2026
@S1m it's as safe as it always was, and as safe as if QCs were impossible. (Which is to say very safe, no one really thinks AES will get surprise broken.)
\PSKs are fine if you can keep them from being compromised. The scheme you excerpted should be fine if auth_secret is not known to the attacker.
View full thread on abyssdomain.expert
0
1
0
Conversation (1)
Showing 0 of 1 cached locally.
Syncing comments from the remote thread. 1 more reply is still loading.
Loading comments...