Hi Freepine, That did the trick, thanks! I was surprised I didn't see much of a speed increase in the (non-cached) connection being established when I dropped down from a 256-bit AES to a 40-bit export DES key. I guess most of the time is gobbled up by the handshake itself.
On Jun 20, 3:01 am, Freepine <[email protected]> wrote: > Hi, SHA1PRNG indicates the preudo-random number generator is based on > SHA-1(a message digest algorithm), it's not the encryption algorithm used > for communication. > You can try SSLSocket.getSupportedCipherSuites() to retrieve the information > of supported cipher suites, and setEnabledCipherSuites to specify the cipher > suites enabled for use on this connection. > > On Fri, Jun 19, 2009 at 11:22 PM, george <[email protected]> wrote: > > > As far as I can see, the only encryption algorithm available for SSL > > connections is the default SHA-1. (Which can be passed as > > SecureRandom.getInstance("SHA1PRNG") into the SSLSocketFactory > > constructor. Is there support for other algorithms such as DES, or > > RC4?
