3 ms·
I'm a bit tired, but can someone explain how "Publishing? Not a great idea" and "Deniable key exchange" fit together? It seems the former says 'just hand our y
by darklajid 11y ago
I'm a bit tired, but can someone explain how "Publishing? Not a great idea" and "Deniable key exchange" fit together?
It seems the former says 'just hand our your key to persons that need it', while the latter seems to say 'make your key available ~everywhere~'? This part even lists key servers as one of the routes others can take to verify your key?
- rinon 11y agoExchanging a key pair specifically for future anonymous communication between two parties using a publicly published identity seems like a good compromise for communicating anonymously with previously unknown parties.
- grugq 11y agoI am a public figure. If you want to contact me via PGP you can find my key easily. When you contact me, you encrypt your message and include your public PGP key. This eliminates the threat of a man in the middle attack. Only one side needs to be authenticated (mine) and it is done publicly. If you and a friend want to discuss something secretly, then you can create new email accounts plus new PGP keys and exchange them out of band, e.g. via USB stick. This will allow you to remain somewhat anonymous in that neither email account nor key are linked to you. As long as you don't taint that compartment, it will be secure against compromising you. That level of secrecy might not be necessary for your given threat model. It is up to you and your interlocutor how you want to secure your comms channel. This guide presents best practices that can be combined into a complete COMSEC plan. This guide is not a strict HOWTO that presents a simple step by step solution for everyone. No such HOWTO can exist. Instead it presents a number of solutions to problems (and attempts to explain what problems they solve, why and how).