[erlang-questions] erlang-bcrypt status

Juan Jose Comellas juanjo@REDACTED
Tue Jun 18 17:08:58 CEST 2013

We've been using the Opscode fork of this library at
https://github.com/opscode/erlang-bcrypt as our source and I have moved
some critical fixes that were sitting as pull requests in the Smarkets
repository to the Opscode one.


On Tue, Jun 18, 2013 at 12:33 AM, Jeremy Ong <jeremy@REDACTED> wrote:

> Hi all,
> The highest profile implementation of the bcrypt algorithm is currently
> the smarkets fork of erlang-bcrypt at
> https://github.com/smarkets/erlang-bcrypt.
> However, activity on this fork has not existed for a year now and I think
> we should reach a consensus on where this library should be officially
> maintained so everybody's patches can coalesce cohesively.
> The issues I see now are build problems on various nixes, a very outdated
> bundled rebar, and a potentially thread safety issue mentioned here:
> https://github.com/smarkets/erlang-bcrypt/pull/9/files.
> I am willing to do this and the fork would be actively maintained at the
> company I work at (Quark Games). However, I want to open up this
> opportunity in case somebody has already done significant work on the
> library and wants to curate it that I am unaware of.
> Cheers,
> Jeremy
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20130618/496152df/attachment.htm>

More information about the erlang-questions mailing list