Skip to content

Commit 77ab7a0

Browse files
committed
update NEWS and other files for 0.9 release
1 parent 1a759b9 commit 77ab7a0

File tree

3 files changed

+20
-0
lines changed

3 files changed

+20
-0
lines changed

MANIFEST.in

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# basic metadata
2+
include MANIFEST.in LICENSE NEWS README.md

NEWS

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,9 @@
1+
* Release 0.9 (01 Oct 2013)
2+
3+
Add secp256k1 curve (thanks to Benjamin Dauvergne). Add deterministic (no
4+
entropy needed) signatures (thanks to slush). Added py3.2/py3.3 compatibility
5+
(thanks to Elizabeth Myers).
6+
17
* Release 0.8 (04 Oct 2011)
28

39
Small API addition: accept a hashfunc= argument in the constructors for

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -241,6 +241,18 @@ signature must use a different one (using the same number twice will
241241
immediately reveal the private signing key). The `sk.sign()` method takes an
242242
entropy= argument which behaves the same as `SigningKey.generate(entropy=)`.
243243

244+
## Deterministic Signatures
245+
246+
If you call `SigningKey.sign_deterministic(data)` instead of `.sign(data)`,
247+
the code will generate a deterministic signature instead of a random one.
248+
This uses the algorithm from RFC6979 to safely generate a unique `k` value,
249+
derived from the private key and the message being signed. Each time you sign
250+
the same message with the same key, you will get the same signature (using
251+
the same `k`).
252+
253+
This may become the default in a future version, as it is not vulnerable to
254+
failures of the entropy source.
255+
244256
## Examples
245257

246258
Create a NIST192p keypair and immediately save both to disk:

0 commit comments

Comments
 (0)