I)ruid on Nostr: Using the PGP key from the keyservers as referenced in your Twitter profile, I get a ...
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 <jimmy@bitcointechtalk.com>" [unknown]
Looks like the correct key:
$ gpg --list-key jimmy
pub rsa2048 2014-03-11 [SCEA]
C1D797BE7D105291228CD70CFAA617E32679E455
uid [ unknown] Jimmy Song <jimmy@bitcointechtalk.com>
uid [ unknown] Jimmy Song <jimmy@offchainshow.com>
uid [ unknown] Jimmy Song <jimmy@programmingblockchain.com>
uid [ unknown] Jimmy Song <jaejoon@gmail.com>
Not sure why GPG is saying it's 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 <jimmy@bitcointechtalk.com>" [unknown]
Looks like the correct key:
$ gpg --list-key jimmy
pub rsa2048 2014-03-11 [SCEA]
C1D797BE7D105291228CD70CFAA617E32679E455
uid [ unknown] Jimmy Song <jimmy@bitcointechtalk.com>
uid [ unknown] Jimmy Song <jimmy@offchainshow.com>
uid [ unknown] Jimmy Song <jimmy@programmingblockchain.com>
uid [ unknown] Jimmy Song <jaejoon@gmail.com>
Not sure why GPG is saying it's a bad signature...