Does anyone have a
solution to help speed up the client side random seed generation for ssl based
connections? There seems to be a 5-10 second delay (depending on the
platform) in the SecureRandom class. I've modified the Security propery of
"securerandom.source" to a static file which increased the connection time in
half (but includes no randomness), but was looking for an alternative to replace
just the SecureRandom class in the jdk crypto classes without having to create a
full blown custom Provider.
I'm looking into
creating a custom native provider to perform the seed generation, but would
rather use another approach if that is possible.
I've seen other
postings regarding ssl connectivity issues, but none concerning the initial
random number generation slowness. I'm sure others are experiencing this
and would appreciate any insights others could provide.
Thanks in
advance...
-Joe
|
