From: Dario Teixeira <darioteixeira@yahoo.com>
To: OCaml Mailing List <caml-list@inria.fr>
Subject: [Caml-list] [ANN] ocaml-safepass 1.0
Date: Mon, 9 Jul 2012 10:43:42 -0700 (PDT) [thread overview]
Message-ID: <1341855822.75593.YahooMailNeo@web111505.mail.gq1.yahoo.com> (raw)
Hallo,
The registration of users with login + password is a common feature in
web sites. And as you know, this login data is a valuable prize for
attackers. Therefore I'm happy to announce the availability of version
1.0 of OCaml-safepass, a simple library offering facilities for the safe
storage of user passwords. By "safe" I mean that passwords are salted
and hashed using the Bcrypt algorithm [1]. Salting prevents rainbow-table
based attacks [2], whereas hashing by a very time-consuming algorithm such
as Bcrypt renders brute-force password cracking impractical.
OCaml-safepass's obvious usage domain are web applications, though it
does not depend on any particular framework. Internally, OCaml-safepass
binds to the C routines from Openwall's Crypt_blowfish [3]. However,
it would be incorrect to describe OCaml-safepass as an OCaml binding
to Crypt_blowfish, because the API it exposes is higher-level and more
compact than that offered by Crypt_blowfish. Moreover, OCaml-safepass's
API takes advantage of OCaml's type-system to make usage mistakes nearly
impossible.
Here is the project website:
http://ocaml-safepass.forge.ocamlcore.org/
The API documentation is also available on online:
http://ocaml-safepass.forge.ocamlcore.org/apidoc/index.html
Feedback is more than welcome!
Best regards,
Dario Teixeira
[1] http://en.wikipedia.org/wiki/Bcrypt
[2] http://en.wikipedia.org/wiki/Rainbow_table
[3] http://www.openwall.com/crypt/
reply other threads:[~2012-07-09 17:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1341855822.75593.YahooMailNeo@web111505.mail.gq1.yahoo.com \
--to=darioteixeira@yahoo.com \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox