-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 2/13/12 4:45 PM, Mark Lim wrote:
> Thanks for offering, but we're already in certification. When
> recertification comes up we'll certainly consider consolidating
> security modules.
Okay. Well, if you're willing to put our code into testi
Thanks for offering, but we're already in certification. When
recertification comes up we'll certainly consider consolidating security
modules.
On 2/13/12 1:33 PM, "Christopher Schultz"
wrote:
>* PGP Signed by an unknown key
>
>Mark,
>
>On 1/6/12 7:05 PM, Mark Lim wrote:
>> We are in the proces
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
On 1/6/12 7:05 PM, Mark Lim wrote:
> We are in the process of upgrading Tomcat 5.5 to Tomcat 7.0.
> These Tomcat deployments use a custom FIPS 140-2 certified JSSE
> implementation for their SSL Connectors.
In case you are interested, Tomcats
There's been one request for follow up so I'll post our current findings.
This is what we've identified that we need to do to get Tomcat running
after moving from 5.5 to 7.0. At this point web application porting can
commence.
1. We used several Tomcat classes (e.g. EndPoint, ServerSocketFactory)
Mark Lim wrote:
>It seems that tomcat is trying the default JSSE implementation despite
>the sslImplementationName attribute being set. Are there internal
>precedence controls or does the classloader hierarchy matter or what?
No, but what makes you assume what you are trying will work?
You hav
We are in the process of upgrading Tomcat 5.5 to Tomcat 7.0. These Tomcat
deployments use a custom FIPS 140-2 certified JSSE implementation for their SSL
Connectors.
In Tomcat 5.5, the Connectors are configured like this:
which works fine. ( a listener appears on 41443 and one can do H
