^All that text and you failed to send an encrypted message...
I think that I know how to encrypt a PGP message. It’s not my fault if you couldn’t decrypt it.
$ gpg -v -v < 2020-11-26.ognasty.asc
[...]
gpg: encrypted with 2048-bit RSA key, ID 0xA338C617DE66E656, created 2014-04-24
"OgNasty <...in the thread, public, but will snip anyway...>"
gpg: using subkey 0x74F2272235988F48 instead of primary key 0x5A00591B2F307E0C
gpg: encrypted with 256-bit ECDH key, ID 0x74F2272235988F48, created 2017-03-29
"Nullius <nullius@nym.zone>"
[...]
Because I used
-r (as usual) and not
-R, anyone reading this thread can see the following without even importing either of our keys. Are you
rsa2048/0xA338C617DE66E656 2014-04-24 [SCE]?
WIth test.asc copied from my forum post—in a VM with a very old GnuPG which does not support ECC, with no keys imported:$ gpg -v -v < test.asc
gpg: armor: BEGIN PGP MESSAGE
:pubkey enc packet: version 3, algo 1, keyid A338C617DE66E656
data: [2047 bits]
gpg: public key is 0xA338C617DE66E656
:pubkey enc packet: version 3, algo 18, keyid 74F2272235988F48
unsupported algorithm 18
gpg: can't handle public key algorithm 18
gpg: public key is 0x74F2272235988F48
:encrypted data packet:
length: unknown
mdc_method: 2
gpg: encrypted with [?] key, ID 0x74F2272235988F48
gpg: public key decryption failed: unknown pubkey algorithm
gpg: encrypted with RSA key, ID 0xA338C617DE66E656
gpg: decryption failed: secret key not available
Of course, this does not prove that it is actually encrypted to your key. There is no way to prove that, without your private key.