Commit 92d15784 authored by Niels Möller's avatar Niels Möller

More on the 2.1 release.

Rev: nettle/NEWS:1.5
parent 3c58fc0c
NEWS for the 2.5 release
This release breaks source and binary compatibility for the
RSA-related functions.
XXX: Remaining: Manual update. Key generation for dsa256.
*Important*: this release breaks source and binary
compatibility for the digital signature functions.
Incompatible changes:
* The functions rsa_md5_sign, rsa_sha1_sign and
rsa_sha256_sign, and the corresponding _digest varians, now
have a return value which callers should check. The functions
return failure if the key is too small for the type of
signature.
* The functions dsa_sign and dsa_verify are renamed to
dsa_sha1_sign and dsa_sha1_verify. The _-digest variants are
renamed similarly. These functions now have a return value
which callers sould check, and they return failure if the
number q is not of the appropriate size.
Other changes:
* Support for sha224, sha384 and sha512.
* Support for digital signatures using rsa-sha512 and
dsa-sha256. Due to lack of official test vectors and interop
testing, this support should be considered somewhat
experimental.
* x86_64 assembler implementation actually included in the
distribution (was accidentally left out in nettle-2.0).
* Configure script now detects if the compiler uses a 32-bit
or 64-bit on x86_64 (prevously did this for sparc only).
Also sets the default location for installing libraries
(libdir) depending on system type andd the ABI used.
* Added the nettle and gmp libraries as dependencies when
linking shared library libhogweed.so. On systems using
shared libraries where such dependencies work (in
particular, ELF systems), it is sufficient to link
applications with -lhogweed. For static linking -lhogweed
-lnettle -lgmp is still required.
* The program pkcs1-conv is extended to also handle dsa keys.
Contributed by Magnus Holmgren.
* Slightly improved sha1 performance on x86.
NEWS for the 2.0 release
......
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