Re: [cryptography] coderman's keys
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 for the public: regarding what's difficult about this key: it maps to an email address that does not exist. most users of PGP don't know how to encrypt to a key that isn't in the key metadata itself. if you're unable to encrypt to a specific key, your OPSEC capabilities are insufficient to use this technology. </$0.02> best regards, -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iL4EAREKAGYFAlJzM7lfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl bnBncC5maWZ0aGhvcnNlbWFuLm5ldDQxQzEyQjhDMzA3RDdFMjE5OEFBNTc4MTY1 QTg0N0U3QzJCOTM4MEMACgkQZahH58K5OAx6KQEAsGPNK3tDWnpjpaLlbgB1WVIw Ynsp+AwO3oghDvcRxJEA/A0schdXYFxr+YX70uWq3GpLI2JCG/iPlDIcBT/R5CSU =v7g0 -----END PGP SIGNATURE-----
On Fri, Nov 1, 2013 at 12:54 AM, coderman <coderman@gmail.com> wrote:
regarding what's difficult about this key: it maps to an email address that does not exist. most users of PGP don't know how to encrypt to a key that isn't in the key metadata itself. if you're unable to encrypt to a specific key, your OPSEC capabilities are insufficient to use this technology. </$0.02>
The problem is encrypting a message to the key, not sending via some little-known Tor hidden mail transport. At least that's MY interpretation of the paragraph above.
participants (2)
-
Bill St. Clair -
coderman