Bill Dortch wrote:
Hmm, that may work with HTTPS, but certainly won't help with Net::SSH,
which depends on OpenSSL::PKey, as well as OpenSSL::BN (which I recently
implemented) and OpenSSL::PKey::DH (which I'm just about done with). Of
course HTTPS support is more critical, but I hate to see us stripping
away functionality (especially when I'm trying to use it!).
Maybe we could break out a separate 'stripped' version for HTTPS-only
support.
Well I'll do you one better...if it's possible, we could provide HTTPS
support out of the box without openssl gem being installed; then users
would only have to install it if they use something more than SSLSocket.
That would be really nice.
Also, the recent 1.1 API changes break some pieces of jopenssl (though
perhaps nothing that's being used). It may be time to think about
splitting it into 1.0x and 1.1x versions.
jopenssl trunk is now using an adapter that's aware of 1.0 and 1.1
interfaces. The big reason we need to try to avoid splitting is that
rubygems doesn't support separate gems of the same version for different
versions of runtime.
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
