Ok, we need to discuss this a bit. I think it's time we rolled
jruby-ossl (OpenSSL) directly into JRuby and maintained it there.
There are many reasons why this will make life easier:
* No requirement to install a gem to get SSL support, which is
sometimes impossible of only SSL sources are available
* Ability to use SSL without loading RubyGems. Less of a gain under
1.9 mode, which always has RubyGems loaded.
* Fewer goofy issues and bug reports due to our stubbed-out versions
not being fully functional and sometimes not properly intercepting SSL
calls that need the gem.
We originally did not include jruby-ossl in JRuby because we (and Sun,
at the time) were concerned about us shipping crypto -- the
BouncyCastle libraries as part of JRuby proper. I've done some
research on the exportability of BouncyCastle, and all signs
(including BC's site and the US government's sites on the subject)
seem to indicate that because BC is open-source and freely available,
all we need to do is notify the US government of our intention to ship
it as part of JRuby. So I think it's time we bit the bullet.
I will handle contacting US gov't folks to confirm this, but in the
meantime I've created the builtin_ssl branch (on github/headius/jruby)
that folds jruby-ossl code back into JRuby proper. It appears to be
passing tests.
Thoughts? Concerns?
- Charlie
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
