From: O Monroy <o.a.monroy@...>
Date: 2014-02-05T03:24:49-05:00
Subject: [ruby-core:60505] Unsubscribe



Sent from my iPhone

> On Feb 4, 2014, at 4:10 PM, dank@kegel.com wrote:
> 
> Issue #9439 has been updated by Dan Kegel.
> 
> 
> +1 on moving OpenSSL out into a gem.
> 
> Note: Apple has marked OpenSSL obsolete, and will probably remove it in a future release of Mac OS X.
> 
> I work at a shop that ships a set of libraries to customers that make use of OpenSSL, and
> although we would like to ship our own, newer, OpenSSL, we probably can't because Ruby apps that
> use both our libraries and system OpenSSL would violate C's One Definition Rule
> by linking in two different OpenSSLs.
> 
> In the long run, the way to minimize pain for all concerned is for all players
> to try to migrate to Apple's preferred TLS API.
> 
> Therefore, I would like to see a gem added for Apple's "Secure Transport API",
> and in my wildest dreams, I'd like both the OpenSSL gem and this gem to be
> more or less interchangable, to ease migration between the two APIs.
> 
> And I'd like a pony.
> 
> ----------------------------------------
> Feature #9439: Remove OpenSSL from stdlib
> https://bugs.ruby-lang.org/issues/9439#change-44909
> 
> * Author: Zachary Scott
> * Status: Open
> * Priority: Normal
> * Assignee: 
> * Category: lib
> * Target version: current: 2.2.0
> ----------------------------------------
> Regarding [ruby-core:59943], I agree with nobu that we should remove OpenSSL from ruby.
> 
> It's become too hard to maintain, and would better serve our users to encourage the use of a different implementation.
> 
> Another benefit of removing OpenSSL is the impact backport fixes have on the release management team.
> 
> Although I haven't yet determined the extent of work required to remove it (ie: tooling, tests, etc). We can discuss them here.
> 
> 
> 
> -- 
> http://bugs.ruby-lang.org/