4 ms·
Follow-up email: http://seclists.org/fulldisclosure/2014/Apr/149 http://seclists.org/fulldisclosure/2014/Apr/149 > Not used anywhere though, just a corpse lyin
by paulannesley 13y ago
Follow-up email: http://seclists.org/fulldisclosure/2014/Apr/149 http://seclists.org/fulldisclosure/2014/Apr/149
> Not used anywhere though, just a corpse lying around in the code. — Jann Horn
- pipeep 13y agoNot in OpenSSL, but Ruby uses it: https://github.com/ruby/ruby/blob/1aa54bebaf274bc08e72f9ad3854c7ad592c344a/ext/openssl/ossl_ssl_session.c#L76 https://github.com/ruby/ruby/blob/1aa54bebaf274bc08e72f9ad38...
- stusmall 13y agoRuby uses a version of it they copied into their source tree. You can't really fault OpenSSL for another project copying one of their internal, static functions. I've never looked at Ruby's code base before. Did they just fork all of OpenSSL? EDIT: I see you made a patch for it. High five!
- pipeep 13y agoThe code in question is a Ruby FFI wrapper for OpenSSL (not a fork). Originally the function wasn't static, so when OpenSSL made it static, Ruby copied the function implementation to their source tree, as to avoid breaking their API.