Commit 7ba5f988 authored by Jesper Louis Andersen's avatar Jesper Louis Andersen
Browse files

v0.12.0 - Add new Curve25519 extensions to the API

* Introduce Curve25519 handling.
* Update and bump README.md
* Add contributor file
parent 3f8979ce
List of people who have contributed to the eNaCl source code:
Alexander Fæhrøy
Jesper Louis Andersen
......@@ -54,7 +54,11 @@ In general, the primitives provided by NaCl are intermediate-level primitives. R
# Versions
## v0.11.x
### v0.12.0
* Introduce an extension interface for various necessary extensions to the eNaCl system for handling the Tor network, thanks to Alexander Fæhrøy (ahf).
* Introduce Curve25519 manipulations into the extension interface.
* Write (rudimentary) QuickCheck tests for the new interface, to verify its correctness.
### v0.11.0
......@@ -63,8 +67,6 @@ In general, the primitives provided by NaCl are intermediate-level primitives. R
* Use test cases which tries to inject `iodata()` rather than binaries in all places where `iodata()` tend to be accepted.
* Fix type for `enacl:box_open/4`. The specification was wrong which results in errors in other applications using enacl.
## v0.10.x
### v0.10.2
Maintenance release. Fix some usability problems with the library.
......@@ -88,12 +90,10 @@ Ultra-late beta; tuning for the last couple of functions which could be nice to
Do note that on Linux and FreeBSD at the *least*, this is the best thing you can do. Relying on `/dev/random` is almost always wrong and gives no added security benefit. Key generation in NaCl relies on `/dev/urandom`. Go relies on `/dev/urandom`. It is about time Erlang does as well.
## v0.9.x
### v0.9.0
Ultra-late beta. Code probably works, but it requires some real-world use before it is deemed entirely stable.
### v0.9.0
Initial release.
# Overview
......
{application, enacl,
[
{description, "Erlang NaCl bindings"},
{vsn, "0.11.0"},
{vsn, "0.12.0"},
{registered, []},
{applications, [kernel, stdlib]},
{env, []}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment