> From: owner-openssl-us...@openssl.org On Behalf Of Jakob Bohm > Sent: Monday, 12 September, 2011 03:52
> On 9/9/2011 10:13 PM, krishnamurthy santhanam wrote: <snip: unclear about key transport or maybe derivation> > The normal way to do this is: > > 1. On the side running openssl, just let openssl handle the > entire process, > including any AES (or other negotiated algorithm) encryption in both > directions with all the required precautions about key reuse etc. > If you insist on at least 256 bit AES, set options in openssl > parameters to > only accept ciphersuites with strong enough ciphers. > > 2. On the side running Java, just let the standard SSL > classes in Java (I > forgot their names, see the JDK docs) handle the entire > process in the same > way. If you insist on at least 256 bit AES, set options in > java SSL class > parameters to only accept ciphersuites with strong enough > ciphers, or if that > is not possible, check the ciphersuite chosen after handshake > and abort if > not strong enough for your purpose. > It is enough to require 'strong' cipher on one of server or client, whichever is more convenient. On Java to use AES 256 at all (optional or required) you must install the JCE 'unlimited' policy from the Sun-now-Oracle website. At least on the Suncle JVM; other JVMs may work differently. This may apply to other 'high' suites also; I haven't checked all. <snip rest> ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
