tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GOMEZ Henri <hgo...@slib.fr>
Subject RE: Tomcat to support other keystore types?
Date Tue, 06 Nov 2001 08:57:36 GMT
And what about supporting other SSL implementation,
different from JSSE ?

I think of course about Cryptix and PureTLS, and I
know a Cryptix developper which is interested providing
us support on that area...

-
Henri Gomez                 ___[_]____
EMAIL : hgomez@slib.fr        (. .)                     
PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



>-----Original Message-----
>From: Bill Barker [mailto:wbarker@wilshire.com]
>Sent: Friday, November 02, 2001 7:43 AM
>To: Tomcat Developers List
>Subject: Re: Tomcat to support other keystore types?
>
>
>This is probably outside of the development plans for 3.2.x.
>I'm +1 for supporting this  in 3.3.1
>I'm going to let the 4.0 people answer for themselves (e.g. I'm +0).
>----- Original Message -----
>From: "Meren, Libby" <LIBBY.MEREN@ca.com>
>To: <tomcat-dev@jakarta.apache.org>
>Sent: Thursday, November 01, 2001 9:30 PM
>Subject: Tomcat to support other keystore types?
>
>
>> Hi,
>>
>> Tomcat currently only supports Sun's default keystore: JKS.  
>Are there any
>> plans to change tomcat to take a keystore type as a 
>parameter, and then
>run
>> using that keystore for it's SSL?  We're currently looking 
>at the code to
>> try and implement our keystore (which implements the
>java.security.keystore
>> interface), however there are many complications.
>>
>> Any help/advice would be very much appreciated.
>>
>> Thanks,
>>
>> Libby Meren
>> Computer Associates
>> Software Engineer, eTrust PKI
>> E-Mail: Libby.Meren@ca.com
>>
>>
>> --
>> To unsubscribe, e-mail:
><mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
>> For additional commands, e-mail:
><mailto:tomcat-dev-help@jakarta.apache.org>
>>
>>
>
>
>*----*
>
>This message is intended only for the use of the person(s) 
>listed above 
>as the intended recipient(s), and may contain information that is 
>PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, 
>you may not read, copy, or distribute this message or any attachment.  
>If you received this communication in error, please notify us 
>immediately 
>by e-mail and then delete all copies of this message and any 
>attachments.
>
>
>In addition you should be aware that ordinary (unencrypted) 
>e-mail sent 
>through the Internet is not secure. Do not send confidential 
>or sensitive 
>information, such as social security numbers, account numbers, 
>personal 
>identification numbers and passwords, to us via ordinary (unencrypted) 
>e-mail. 
>
>--
>To unsubscribe, e-mail:   
<mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>

--
To unsubscribe, e-mail:   <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>


Mime
View raw message