Ämne:Re: [dcdev] Encrypting ADC - a second approach
Till:Direct Connect developers
Lose how? The symmetric keys are temporary for each session/connection,2) No perfect forward secrecy - lose the key to someone and any
recorded data can be decrypted (authorities spring to mind)
and never stored. How the assymetric keys are locally stored, can be made
safe quite easily. However, this problem occurs to any program
implementing asymmetric ciphers. In Unix you depend on filesystem rights
for the private keys etc.
Surely one would like Some sort of negotation though, I fully agree on
What packetfilter problems? Sure it's identifyable unless one uses a
common cipher-handshake such as ssl/tls gives you. I don't have an
opinion on whether this is an issue or not... Unless 'they' can read the
traffic, do we care if they know what it's for? Maybe.
Only support encrypted connections is by far the easiest way.
I personally just dislike the so called 'certificates' that are being
generated. I'm not sure they fit a p2p system. They depend on dns names
and so on iirc...