...
Dabs and Ayle56
You both have a message, although Dabs got one that might be incorrectly formatted (the LATTER message is probably the right one).
I got your message and sent a reply.
Recently a guy called Craig Steven Wright attempted to trick the world into believing he was the real Satoshi Nakamoto. He created a PGP key, signed a message, and tried to pass it off as something posted on the internet the same day Satoshi posted PGP content.
Someone analyzed the PGP message header and discovered it used a modern version of crypto algorithms, rather than the old version of crypto algorithms from years ago that the real Satoshi's PGP content used.
Some of the information in a PGP header can be read by anyone with the right software. The Key ID in the header can compromise your anonymity, as this quote from a webpage shows. If it's important there are ways of removing the Key ID from PGP message headers to make it more anonymous.
http://tech.michaelaltfield.net/2013/10/19/analyzing-pgp-content/This post attempts to answer the following question: If an evesdropper intercepts a message encrypted with gpg, how much information will they be able to extract from the message without a decryption key?
I will show the unencrypted metadata added to a GPG-encypted message, and I will present commands that can be used to extract this unencrypted metadata.
In the below execution, I demonstarte the creation of a key, the encryption of a file, the deletion of the secret key, and the analysis of the encrypted file without the ability to decrypt its contents
...
Now that all the files are created and the secret key has been deleted, let’s try to analyze the pgp file to see what unencrypted data we can pull out.
root@Microknoppix:/tmp/test# gpg --list-packets test.txt.gpg
:pubkey enc packet: version 3, algo 1, keyid D65FA0A95D0D3E9C
data: [1023 bits]
:encrypted data packet:
length: 80
mdc_method: 2
gpg: encrypted with RSA key, ID 5D0D3E9C
gpg: decryption failed: secret key not available
As you can see above, this message was encrypted using the key “D65FA0A95D0D3E9C” using RSA.
Let’s try another (more human readable) tool for dumping unencrypted data from PGP files: PGPdump.
root@Microknoppix:/tmp/test# pgpdump test.txt.gpg
Old: Public-Key Encrypted Session Key Packet(tag 1)(140 bytes)
New version(3)
Key ID - 0xD65FA0A95D0D3E9C
Pub alg - RSA Encrypt or Sign(pub 1)
RSA m^e mod n(1023 bits) - ...
-> m = sym alg(1 byte) + checksum(2 bytes) + PKCS-1 block type 02
New: Symmetrically Encrypted and MDC Packet(tag 18)(80 bytes)
Ver 1
Encrypted data [sym alg is specified in pub-key encrypted session key]
(plain text + MDC SHA1(20 bytes))
As you can see, pgpdump seems to have pulled the same data, but it’s expounded a bit on what RSA does. It also appears to include information about a symmetric key, which makes sense but isn’t obvious from the `gpg—list-packets` command above.
Now, let’s try to hide the recipient of the message using `gpg—hidden-recipient` instead of `gpg—recipient`.
...
And below we peek at the gpg file’s packet’s headers to see if we can still see the recipeient.
root@Microknoppix:/tmp/test# gpg --list-packets test.txt.gpg
:pubkey enc packet: version 3, algo 1, keyid 0000000000000000
data: [1022 bits]
:encrypted data packet:
length: 80
mdc_method: 2
gpg: encrypted with RSA key, ID 00000000
gpg: decryption failed: secret key not available
root@Microknoppix:/tmp/test# pgpdump test.txt.gpg
Old: Public-Key Encrypted Session Key Packet(tag 1)(140 bytes)
New version(3)
Key ID - 0x0000000000000000
Pub alg - RSA Encrypt or Sign(pub 1)
RSA m^e mod n(1022 bits) - ...
-> m = sym alg(1 byte) + checksum(2 bytes) + PKCS-1 block type 02
New: Symmetrically Encrypted and MDC Packet(tag 18)(80 bytes)
Ver 1
Encrypted data [sym alg is specified in pub-key encrypted session key]
(plain text + MDC SHA1(20 bytes))
Success! We’ve hidden the key id of the recipient!