Not-Yet-Commons-SSL currently has NO affiliation with the Apache Software Foundation (apache.org), but we're hoping to start Incubation one day.
Current Version (March 16th, 2015): | ||||
---|---|---|---|---|
Full source: | not-yet-commons-ssl-0.3.17.zip | 15 MB | Alpha | MD5: abbba5b3d0a67a0ff50bc9716bc5c6f8 |
Binary only: | not-yet-commons-ssl-0.3.17.jar | 991KB | Alpha | MD5: f81f13575bd317ab4d9a6e73f58d4f36 |
Previous Version (September 23rd, 2014): | ||||
Full source: | not-yet-commons-ssl-0.3.16.zip | 5.8MB | Alpha | MD5: a76a059767d3e67881da1680a32f16a8 |
Binary only: | not-yet-commons-ssl-0.3.16.jar | 267KB | Alpha | MD5: ac3c7c1722222970677e723c22f1d4c8 |
All Previous Versions (use "svn export"): | ||||
/svn/not-yet-commons-ssl/tags/ |
Future versions will definitely break the current API in a non-reverse compatible way. After commons-ssl-0.5.0, though, we plan on always being reverse compatible with ourselves.
openssl enc -K [key] -iv [IV]
.SSLClient client = new SSLClient(); client.addAllowedName( "www.cucbc.com" ); Socket s = client.createSocket( "cucbc.com", 443 );This technique is also useful if you don't want to use DNS, and want to connect using the IP address.
SSLClient server = new SSLServer(); server.useTomcatSSLMaterial();
java.lang.RuntimeException: Export restriction: this JSSE implementation is non-pluggable. at com.sun.net.ssl.internal.ssl.SSLSocketFactoryImpl.checkCreate(DashoA6275) at sun.net.www.protocol.https.HttpsClient.afterConnect(DashoA6275) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(DashoA6275) at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:560) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getOutputStream(DashoA6275)Silly Java - I'm still using your JSSE implementation, I'm just wrapping it!
"javax.net.ssl.keyStore"
and "javax.net.ssl.trustStore"
ssl.setCheckCRL( true/false )
Note: CRL is an abbreviation for "Certificate Revocation List"true
by default. If you're using SSLClient, then the remote
server's certificate chain is checked. If you're using SSLServer, CRL checking is ignored unless
client certificates are presented. Commons-SSL tries to perform the CRL check against each certificate in
the chain, but we're not sure if we always know the entire chain.
Implementation note:
To reduce memory consumption all CRL's are saved to disk using
File.createTempFile()
and File.deleteOnExit()
.
CRL's are re-downloaded every 24 hours. To reduce disk IO
the "pass/fail" result of a CRL check for a given X.509 Certificate is cached using the 20 byte SHA1 hash of the
certificate as the key. The cached "pass" result is discarded every 24 hours. The cached "fail" result is retained
until the JVM restarts.
ssl.setCheckExpiry( true/false )
ssl.setCheckHostname( true/false )
Support added for certificates with wildcards in the CN field (e.g. *.credential.com). Java already had this, to be fair. We broke it by accident!
s: CN=*.credential.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/cps (c)05, OU=businessprofile.geotrust.com/get.jsp?GT27402892, O=*.credential.com, C=CA i: CN=Equifax Secure Global eBusiness CA-1, O=Equifax Secure Inc., C=US
KeyStoreBuilder
"java -cp commons-ssl-0.3.4.jar org.apache.commons.ssl.KeyStoreBuilder