Tomcat to support other keystore types?

2001-11-01 Thread Meren, Libby

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: [EMAIL PROTECTED]


--
To unsubscribe, e-mail:   mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]




Re: Tomcat to support other keystore types?

2001-11-01 Thread Bill Barker

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 [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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: [EMAIL PROTECTED]


 --
 To unsubscribe, e-mail:
mailto:[EMAIL PROTECTED]
 For additional commands, e-mail:
mailto:[EMAIL PROTECTED]




**

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:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]