Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@apache.org Received: (qmail 84615 invoked from network); 7 Nov 2001 04:12:33 -0000 Received: from unknown (HELO osaka.betaversion.org) (192.18.49.133) by daedalus.apache.org with SMTP; 7 Nov 2001 04:12:33 -0000 Received: (qmail 14971 invoked from network); 7 Nov 2001 04:15:05 -0000 Received: from nagoya.betaversion.org (192.18.49.131) by osaka.betaversion.org with SMTP; 7 Nov 2001 04:15:05 -0000 Received: (qmail 24257 invoked by uid 97); 7 Nov 2001 04:12:25 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-dev@jakarta.apache.org Received: (qmail 24241 invoked by uid 97); 7 Nov 2001 04:12:24 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Developers List" Reply-To: "Tomcat Developers List" Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 24230 invoked from network); 7 Nov 2001 04:12:24 -0000 Message-ID: <000801c16742$d2462780$1b7d0304@vz.dsl.genuity.net> From: "Bill Barker" To: "Tomcat Developers List" References: Subject: Re: Tomcat to support other keystore types? Date: Tue, 6 Nov 2001 20:15:22 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archived: msg.XXzxtWMa@sneezy X-Filter-Version: 1.4.5 (sneezy) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I've checked in the modifications to PoolTcpConnector to allow plugging in another SSL provider. Now he just has to create a class extending o.a.t.util.net.ServerSocketFactory that works with his SSL implementation, and then put it's class as the value to the socketFactory attribute in Http10Interceptor. ----- Original Message ----- From: "GOMEZ Henri" To: "Tomcat Developers List" Cc: "Eric Rescorla" Sent: Tuesday, November 06, 2001 12:35 PM Subject: RE: Tomcat to support other keystore types? > Good, > > I'll forward to the PureTLS developper :) > > > - > 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: Tuesday, November 06, 2001 7:45 PM > >To: Tomcat Developers List > >Subject: Re: Tomcat to support other keystore types? > > > > > >This is also relatively easy, from the TC side. A little bit of code > >re-organization should make it transparent. The main work would be the > >implementation of o.a.t.util.net.ServerSocketFactory that > >works with the SSL > >implementation. > >----- Original Message ----- > >From: "GOMEZ Henri" > >To: "Tomcat Developers List" > >Sent: Tuesday, November 06, 2001 12:57 AM > >Subject: RE: Tomcat to support other keystore types? > > > > > >> 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" > >> >To: > >> >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: > >> > > >> >> For additional commands, e-mail: > >> > > >> >> > >> >> > >> > > >> > > >> >*----* > >> > > >> >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: > >> > >> For additional commands, e-mail: > > > >> > >> -- > >> To unsubscribe, e-mail: > > > >> For additional commands, e-mail: > > > >> > >> > > > > > >*----* > > > >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: > > For additional commands, e-mail: > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > *----* 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: For additional commands, e-mail: