I’ve never used this before besides verifying Electrum, and kind of played around finding @Ognasty’s certificate on the server beforehand. There are three potential entries there (which does not mean they are really his), so I’m not sure if I’ve used the correct one, since I imported a couple of them.
-----BEGIN PGP MESSAGE-----
hQEMA6M4xhfeZuZWAQf6AtH14WhLkQhzGQtBY05wlu4zcyJ3LCTtDzeJbXyxlnwv
UCsE0GOz9qZn17nM5EN91O3ZlcwerWQyMarguwIKL3/vD/5+sSORegHn328/rfvA
etTq/1bFGKokOxRoSE4uyA41DHqLjKMfU4rTmsHhWSca2BacPQE7w/1eqq9pPyC/
0M44QjlPIALlAA5QeybWXmuzrVluUpWvrAi9nrEO5F0uqg936TxvzMenNdyMKydP
2FeGwHxRYwuBsSyHFou3e1gUuhAJr7M89ib9ALTWJlQPAa9ubC+SHS2r+LJvVb+2
Y7SdBhIUWcvwY1GzBdaNf5dFw3H/co3lJyFnMBii7tJbAVnA/bCNUIMuRPXAheIl
06WEsb9wX6xiBCynUkrlZHeC85Lt0Tr60mFi2JXrQIlgXrRm69zy6xbQtrj0dAgd
eepfn2tW7fZQAmFIL2V0h3aANNBOg/+CTLyXhQ==
=QyuJ
-----END PGP MESSAGE-----
I’d just like to know (no merits) if I used the correct one. It seems so, since all valid signed messages contain the same prefix (and using the other imported certificate renders a different prefix). Prefix (first few characters) are the header, and include:
pgpdump <ASCII data>
Old: Public-Key Encrypted Session Key Packet(tag 1)(268 bytes)
New version(3)
Key ID - 0xA338C617DE66E656
Pub alg - RSA Encrypt or Sign(pub 1)
RSA m^e mod n(2048 bits) - ...
-> m = sym alg(1 byte) + checksum(2 bytes) + PKCS-1 block type 02
New: Symmetrically Encrypted and MDC Packet(tag 18)(98 bytes)
Ver 1
Encrypted data [sym alg is specified in pub-key encrypted session key]
(plain text + MDC SHA1(20 bytes))
(I’ve used
https://www.lirnberger.com/tools/pgpdump/ to see the header info).