Global Feed Post Login
Replying to Avatar I)ruid

Using the PGP key from the keyservers as referenced in your Twitter profile, I get a bad signature:

$ gpg --verify jimmy.msg

gpg: Signature made Fri 03 Feb 2023 04:20:45 AM AST

gpg: using RSA key C1D797BE7D105291228CD70CFAA617E32679E455

gpg: BAD signature from "Jimmy Song " [unknown]

Looks like the correct key:

$ gpg --list-key jimmy

pub rsa2048 2014-03-11 [SCEA]

C1D797BE7D105291228CD70CFAA617E32679E455

uid [ unknown] Jimmy Song

uid [ unknown] Jimmy Song

uid [ unknown] Jimmy Song

uid [ unknown] Jimmy Song

Not sure why GPG is saying it's a bad signature...

Avatar
shafemtol 2y ago

His client mangled the npub in the plaintext as per NIP-08, your client might show the mangled part as "@jimmysong". If you replace that text with the npub, you should be able to verify it.

Reply to this note

Please Login to reply.

Discussion

No replies yet.