On Sat, 16 Oct 2004, Ulrich Meis wrote:
> [here's a patch to customize ssl.]
>
I've applied a modified version of this patch. I moved the Driver.makeSSL
implementation into it's own class to not use @SSL@ everywhere. I renamed
the sslfactoryargs to sslfactorarg because it really is one argument. If
the user chooses to encode multiple arguments into it, that's really his
own business. I put a NonValidatingFactory class in to demonstrate
how this can work and provide the most requested functionality.
Questions:
In the non-validating factory I have a SSLContext.getInstance("TLS"), but
I've also seen it use "SSL". Is either preferred or does it matter for
pg?
I've been building the jdbc2ee jar files against the actual j2sdkee1.2.1,
not just the jdbc optional package. This includes support for
javax.net.ssl.SSLSocketFactory, but not javax.net.ssl.SSLContext and
associated classes which are in com.sun.net.ssl instead. So at the moment
I've modified the ssl requirements to not build ssl into this
particular jar. What do we want to do about this:
- nothing, the ee really meant datasource and was never meant to
include ssl
- make the existing ssl support work by not building the
NonValidingFactory class
- make everything work by building the NonValidatingFactory by importing
from com.sun.net.ssl instead.
Kris Jurka
