On 9/8/2013 10:16 AM, Randolph D. wrote:
2013/9/7 Niklas Schnelle <niklas.schne...@gmail.com
<mailto:niklas.schne...@gmail.com>>
Dear OpenSSL users,
what can be done to improve the situation.
One option is to switch from central SSL Certs to selfsigned SSL Certs
in a p2p environment
http://en.wikipedia.org/wiki/Self-signed_certificate
SSL sends the key over D/H exchange, which could be attacked by MITM.
One better option would be to send the key for SSL over an AES End to
End encryption.
http://goldbug.sf.net
is a secure multi encrypting messenger, which provides e.g. the AES over
RSA and then third uses OpenSSL in a p2p environment with self signed
certificates as a channel, to send the AES encrypted message over it.
You obviously understand nothing about crypto.
The problem is not how the certificates are distributed but how the
crypto that uses the certificates is done.
And when I looked at the Goldbug code I found so many signs of bad
coding that I wouldn't recommend it for anything without a competent
redesign and reimplementation, this time with proper expert reviewed
protocol docs.
It would be good, if the SSL cert could be exportable to be sent as well
over AES and not DH.
AES alone is completely vulnerable to man-in-the-middle attacks and to
after-the-fact decryption once the reused key has been cracked or
confiscated. DH is only vulnerable to man-in-the-middle. RSA alone is
vulnerable only to after-the-fact decryption. DH followed by a digital
signature (RSA, ElGamal, DSA, SRP etc.) on the key exchange messages is
vulnerable to neither problem, and this is what SSL's EDH and ECDH
suites use (SSL also has suites that omit the EDH/ECDH part, those are
vulnerable to after-the-fact decryption).
Now regardless of what crypto you use, you remain vulnerable to 3
things:
- Bad random numbers.
- Algorithms that are not as secure as expected/advertised. No one
knows if some secret agency has cracked one of the currently trusted
algorithms and not told us, similar to what happened to the German
Enigma algorithm during world war II and just after (Enigma machines
were sold to newly freed colonies by countries that knew that Enigma
had been secretly cracked during the war).
- Badly designed protocols that allow cracking the transmission without
cracking any of the quality parts it was made from. The BEAST and CRIME
attacks against some versions of SSL do just that.
This is the homework, OpenSSL developers have to do to provide that in
their library for self signed certificates, that they can be sent over
different ways than just over Diffie-Hellmann-Exchange.
What needs to be done to establish an SSL connection using an AES
channel to share the secret?
Your are wrong, see above.
Enjoy
Jakob
--
Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com
Transformervej 29, 2730 Herlev, Denmark. Direct +45 31 13 16 10
This public discussion message is non-binding and may contain errors.
WiseMo - Remote Service Management for PCs, Phones and Embedded
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
