rust-secp256k1-unsafe-fast/Cargo.toml

[package]

name = "secp256k1"
version = "0.3.0"
authors = [ "Dawid Ciężarkiewicz <dpc@ucore.info>",
            "Andrew Poelstra <apoelstra@wpsoftware.net>" ]
license = "CC0-1.0"
homepage = "https://github.com/apoelstra/rust-secp256k1/"
repository = "https://github.com/apoelstra/rust-secp256k1/"
documentation = "https://www.wpsoftware.net/rustdoc/secp256k1/"
description = "Rust bindings for Pieter Wuille's `libsecp256k1` library. Implements ECDSA for the SECG elliptic curve group secp256k1 and related utilities."
keywords = [ "crypto", "ECDSA", "secp256k1", "libsecp256k1", "bitcoin" ]
readme = "README.md"

[lib]
name = "secp256k1"
path = "src/lib.rs"

[features]
unstable = []

[dependencies]
arrayvec = "0.3"
rand = "0.3"
libc = "0.1"
rustc-serialize = "0.3"
serde = "0.6"
serde_json = "0.6"
Initial (failing) implementation. 2014-07-07 05:41:22 +00:00			`[package]`

Change name to secp256k1 from bitcoin-secp256k1-rs [breaking-change] 2015-03-25 22:20:44 +00:00			`name = "secp256k1"`
[BREAKING CHANGE] Make PK::from_secret_key() return a Result; change from_ffi functions to From impls If you try to call PublicKey::from_secret() key with an incapable context it will now return an error. Before it would pass through to the underlying library which would terminate the process, something we strive to never expose. Also change the from_ffi functions on various types to impl's of From to be more Rustic. We cannot change the from_slice functions because they have error returns. Also add a Secp256k1::without_caps() function which creates a capability-less context. I find myself using this in so many places downstream that it seems appropriate. 2015-10-14 14:35:02 +00:00			`version = "0.3.0"`
Generate keys from Fortuna rather than always using the OsRng When creating a Secp256k1, we attach a Fortuna CSRNG seeded from the OS RNG, rather than using the OS RNG all the time. This moves the potential RNG failure to the creation of the object, rather than at every single place that keys are generated. It also reduces trust in the operating system RNG. This does mean that Secp256k1::new() now returns an IoResult while the generate_* methods no longer return Results, so this is a breaking change. Also add a benchmark for key generation. On my system I get: test tests::generate_compressed ... bench: 492990 ns/iter (+/- 27981) test tests::generate_uncompressed ... bench: 495148 ns/iter (+/- 29829) Contrast the numbers with OsRng: test tests::generate_compressed ... bench: 66691 ns/iter (+/- 3640) test tests::generate_uncompressed ... bench: 67148 ns/iter (+/- 3806) Not too shabby :) [breaking-change] 2014-09-01 03:26:02 +00:00			`authors = [ "Dawid Ciężarkiewicz <dpc@ucore.info>",`
Fix typo in Andrew's email address; remove rust-crypto dependency 2015-05-04 15:33:53 +00:00			`"Andrew Poelstra <apoelstra@wpsoftware.net>" ]`
Update Cargo.toml for crates.io metadata; this marks the "official" 0.1.0 release 2015-05-04 15:26:45 +00:00			`license = "CC0-1.0"`
			`homepage = "https://github.com/apoelstra/rust-secp256k1/"`
			`repository = "https://github.com/apoelstra/rust-secp256k1/"`
			`documentation = "https://www.wpsoftware.net/rustdoc/secp256k1/"`
			description = "Rust bindings for Pieter Wuille's `libsecp256k1` library. Implements ECDSA for the SECG elliptic curve group secp256k1 and related utilities."
			`keywords = [ "crypto", "ECDSA", "secp256k1", "libsecp256k1", "bitcoin" ]`
			`readme = "README.md"`
Initial (failing) implementation. 2014-07-07 05:41:22 +00:00
Add .travis.yml, update tests and Cargo.toml for upstream changes 2014-08-18 01:55:07 +00:00			`[lib]`
Change name to secp256k1 from bitcoin-secp256k1-rs [breaking-change] 2015-03-25 22:20:44 +00:00			`name = "secp256k1"`
Rename secp256k1.rs to lib.rs 2015-04-09 15:35:38 +00:00			`path = "src/lib.rs"`
Generate keys from Fortuna rather than always using the OsRng When creating a Secp256k1, we attach a Fortuna CSRNG seeded from the OS RNG, rather than using the OS RNG all the time. This moves the potential RNG failure to the creation of the object, rather than at every single place that keys are generated. It also reduces trust in the operating system RNG. This does mean that Secp256k1::new() now returns an IoResult while the generate_* methods no longer return Results, so this is a breaking change. Also add a benchmark for key generation. On my system I get: test tests::generate_compressed ... bench: 492990 ns/iter (+/- 27981) test tests::generate_uncompressed ... bench: 495148 ns/iter (+/- 29829) Contrast the numbers with OsRng: test tests::generate_compressed ... bench: 66691 ns/iter (+/- 3640) test tests::generate_uncompressed ... bench: 67148 ns/iter (+/- 3806) Not too shabby :) [breaking-change] 2014-09-01 03:26:02 +00:00
Update Travis to use travis-cargo 2015-07-28 17:38:01 +00:00			`[features]`
			`unstable = []`

Change rand crate to crates.io version 2015-03-25 23:57:16 +00:00			`[dependencies]`
[API BREAK] Update for new libsecp256k1 API 2015-07-28 16:03:10 +00:00			`arrayvec = "0.3"`
Update Cargo.toml for crates.io metadata; this marks the "official" 0.1.0 release 2015-05-04 15:26:45 +00:00			`rand = "0.3"`
			`libc = "0.1"`
			`rustc-serialize = "0.3"`
Update serde dep to 0.6 from 0.3 2015-09-20 17:52:46 +00:00			`serde = "0.6"`
			`serde_json = "0.6"`
Change rand crate to crates.io version 2015-03-25 23:57:16 +00:00