Custom fork of rust-secp256k1 with unsafe modifications for higher speed. Unsuitable for production.

Andrew Poelstra 9889090784 Overhaul interface to use zero-on-free SecretKeys ... Using the `secretdata` library, we can store SecretKeys in such a way that they cannot be moved or copied, and their memory is zeroed out on drop. This gives us some assurance that in the case of memory unsafety, there is not secret key data lying around anywhere that we don't expect. Unfortunately, it means that we cannot construct secret keys and then return them, which forces the interface to change a fair bit. I removed the `generate_keypair` function from Secp256k1, then `generate_nonce` for symmetry, then dropped the `Secp256k1` struct entirely because it turned out that none of the remaining functions used the `self` param. So here we are. I bumped the version number. Sorry about this.		2014-09-12 08:28:26 -05:00
src	Overhaul interface to use zero-on-free SecretKeys	2014-09-12 08:28:26 -05:00
.gitignore	Add gitignore	2014-08-04 19:59:58 -04:00
.travis.yml	Travis speaks rust now :D	2014-08-27 10:58:24 -07:00
Cargo.toml	Overhaul interface to use zero-on-free SecretKeys	2014-09-12 08:28:26 -05:00
LICENSE	Add `LICENSE`.	2014-08-10 16:23:40 -07:00
LICENSE-CC0	Add CC0 license and header to all files	2014-08-11 19:26:45 -07:00
Makefile	Initial (failing) implementation.	2014-07-06 22:41:22 -07:00