NEWS

User-Visible Changes in python-ed25519

* Release 1.5 (01-Jun-2019)

Fixed 64-bit windows compatibility, thanks to Theodore "okready" Cipicchio
for the analysis and patch.

Update test coverage to pythons 2.7, 3.4, 3.5, 3.6, and 3.7. Removed 2.6 and
3.3.

Recommend PyNaCl over this package: faster, better-maintained, more features.


* Release 1.4 (03-Jul-2014)

Added pypy3 compatibility, thanks to Miroslav Shubernetskiy. Updated to
versioneer-0.15.


* Release 1.3 (28-Sep-2014)

Added python3.3/3.4 compatibility, thanks to Jan Gerber. According to our
ongoing Travis-CI test coverage, we are now compatible with pythons 2.6, 2.7,
3.3, and 3.4 . Also updated to versioneer-0.11 (which supports py3).


* Release 1.2 (22-Jul-2013)

Don't require C99 features that are lacking on some Microsoft compilers.
Thanks to Samuel "Dcoder" Neves for the patch, via pycryptopp.


* Release 1.1 (15-Feb-2012)

Fix a segfault that occurred on 64bit systems, at least on Fedora/gcc-4.7,
resulting from using the wrong sized variable. Many thanks to Samuel "Dcoder"
Neves for tracking down the problem.


* Release 1.0 (09-Feb-2012)

Minor changes: remove mention of the unimplemented base62 encoding, update to
versioneer-0.7 to make development smoother.


* Release 0.9 (06-Jan-2012)

This release adds compatibility with python2.4, making this library
compatible with py2.4, 2.5, 2.6, and 2.7 . In the long run, our compatibility
target is probably 2.6 through 3.2, but py3 requires some deeper changes. In
the meantime, it'd be nice to have at least one version which can be used by
2.4 (this might be the last, though).


* Release 0.8 (19-Nov-2011)

This release probably adds Windows compatibility. To enable this, the
upstream C code which calls sleep() was removed: crypto_sign_keypair() was
removed from ed25519.c, and randombytes.c and randombytes.h were deleted
entirely. The Python code (in ed25519.create_keypair) wasn't using
crypto_sign_keypair() anyways: it switched to using os.urandom() and
crypto_sign_publickey() in 0.5 .


* Release 0.7 (17-Nov-2011)

The SigningKey.to_ascii() method was modified to return an encoded seed (32
bytes) rather than the full private key (64 bytes). The SigningKey()
constructor will accept either.

Unit tests, known-answer tests, and speed benchmarks can now be run through
setup.py (after building):

 python setup.py build
 python setup.py test
 python setup.py test_kat
 python setup.py speed

A power-on self test (which takes about 10ms) was added, to throw an
AssertionError during import if any of the basic keygen/sign/verify
operations are broken.


* Release 0.6 (16-Nov-2011)

This release fixes execution of unit tests and import errors when run from
inside the source tree: the 0.5 release was quite broken (having a directory
named 'ed25519' in the source tree's root interfered with imports from the
expected build/... subdirectory), and manual testing failed to catch the
problem (because import found a locally-installed copy in /usr/local). The
source tree has been rearranged to keep this from happening. 

The (small) unit tests are now installed along with the code. The large
Known-Answer-Tests (about 2.5MB) are not, to keep the installed size low
(about 600kB, most of which is the binary .so).

The 0.6 release also improves the version-string generation code, using
python-versioneer-0.1 .


* Release 0.5 (12-Nov-2011)

In this release, the .to_string() method was renamed to .to_bytes(), since
the output is a non-printable binary bytestring.

It also adds prefix= and encoding= arguments to most data-handling methods
(key-object constructors, key-serialization, sign, and verify). These can
help with version-checking and JSON encoding.

The create_keypair() function now takes an entropy= argument, which is called
just like os.urandom, and can be used to deterministically generate keys.
This is most useful for unit tests.