# Re: Secure Sockets API

David Brownell (db@Eng)
Mon, 26 Oct 1998 10:17:09 -0800

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Levinshtein, Gal: "RE: Secure Sockets API"
- Previous message: Jan Luehe: "Re: JCE license"
- Maybe in reply to: Levinshtein, Gal: "Secure Sockets API"

Note that you can configure some HTTPS servers not to use RSA or RC4
ciphers, in which case you won't need that native code to get both
client and server to support some common cipher suite. Recent
versions of Apache, for example, using SSLeay (Stronghold, etc).

The interesting flavors have names like SSL_DHE_DSS_WITH_DES_CBC_SHA;
the "DHE_DSS" bit will always be there, DES might be DES40 or (much
slower) 3DES_EDE instead.

- Dave

Jeff Nisewanger wrote:
>
> > It's possible that the native methods library (libjssl.so or
> > libjsafe.so depending upon which release) is not in your
> > LD_LIBRARY_PATH on Solaris. For windows this would be jssl.dll or
> > jsafe.dll.
>
> Also, for windows you need to have the .dll file in your
> PATH environment variable.

- Next message: Levinshtein, Gal: "RE: Secure Sockets API"
- Previous message: Jan Luehe: "Re: JCE license"
- Maybe in reply to: Levinshtein, Gal: "Secure Sockets API"