News for hackers. Stuff that matters.
Re:OpenSSL vulnerable to timing attack? by paulannesley on Thursday April 10, 2014 @08:35PM (#7570579)
Follow-up email: http://seclists.org/fulldisclosure/2014/Apr/149

> Not used anywhere though, just a corpse lying around in the code. — Jann Horn

Re:OpenSSL vulnerable to timing attack? by pipeep on Thursday April 10, 2014 @08:43PM (#7570607)
Re:OpenSSL vulnerable to timing attack? by stusmall on Thursday April 10, 2014 @09:34PM (#7570777)
Ruby 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!

Re:OpenSSL vulnerable to timing attack? by pipeep on Thursday April 10, 2014 @10:27PM (#7570926)
The 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.