-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 08/19/2014 03:30 PM, Richard Moore wrote: > Oh, I see. I misread, thinking you wanted the dev team to have a > private key and share the public key, similar to alerts. But each > peer would have a public/private key pair and use something akin to > ECDH for a symmetric key and transport using a block cipher? > > How would you share the public key? If I were a man-in-the-middle, > I could intercept the public key, generate my own and pass that > along and then decouple the pipe when the other side shares their > public key. > > Also, you should not ignore your SSH fingerprint, as you exactly > open yourself to mitm attacks.
http://curvecp.org If that's not acceptable, even using TLS with self-signed certificates would be an improvement. - -- Support online privacy by using email encryption whenever possible. Learn how here: http://www.youtube.com/watch?v=bakOKJFtB-k -----BEGIN PGP SIGNATURE----- iQEcBAEBCAAGBQJT83Y1AAoJEMP3uyY4RQ21aqUH/3rGvgz3J6UYY2Qb2qzNoucB QqIj4fByZncX7Fhx5YK6fc6QoLr4Oqxd+zgbJ3ghrLtAJ7dm61iLmmib8MuDz2K1 kQj8xmZhWuUFI26bjK54RlKoWg46XFKNKcaVub6JmVg9dH8mX86mF746KnR5ZqdX BuehWoEqcHlY3JkrTgOGpHjT/EGScZQxzJHzsBOfUJuX12lFtzcWzBTZyo5K8fD+ 6eub3i6Fc4qn/c788UVFsmHeWV+NCeB1/y94V1+peIPWYhrZO+FVm+xEflG4U81Q MRejqNjFT8ztT5vRHx1qJsmIgnzT0SXfh+FRt0hdqJizjlmyntMmCXjFmtnIeT8= =9qWl -----END PGP SIGNATURE-----
0x38450DB5.asc
Description: application/pgp-keys
------------------------------------------------------------------------------
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
