rust-secp256k1-unsafe-fast/Cargo.toml

[package]

name = "secp256k1"
version = "0.9.2"
authors = [ "Dawid Ciężarkiewicz <dpc@ucore.info>",
            "Andrew Poelstra <apoelstra@wpsoftware.net>" ]
license = "CC0-1.0"
homepage = "https://github.com/rust-bitcoin/rust-secp256k1/"
repository = "https://github.com/rust-bitcoin/rust-secp256k1/"
documentation = "https://docs.rs/secp256k1/0.8.4/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"

build = "build.rs"
[build-dependencies]
gcc = "0.3"

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

[features]
unstable = []
default = []
fuzztarget = []

[dev-dependencies]
rand = "0.3"

[dependencies]
libc = "0.2"

[dependencies.rand]
version = "0.3"
optional = true
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"`
bump version to 0.9.2 2018-06-04 19:37:50 +00:00			`version = "0.9.2"`
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"`
update github links in Cargo.toml, bump version number to republish 2018-03-05 19:42:39 +00:00			`homepage = "https://github.com/rust-bitcoin/rust-secp256k1/"`
			`repository = "https://github.com/rust-bitcoin/rust-secp256k1/"`
			`documentation = "https://docs.rs/secp256k1/0.8.4/secp256k1/"`
Update Cargo.toml for crates.io metadata; this marks the "official" 0.1.0 release 2015-05-04 15:26:45 +00:00			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
Switch to static linking of secp256k1 Pieter moved some stuff I need into the contrib/ directory which does not expose anything through the shared lib, so I need to statically link. I might also use this to do evil things to expose the SHA256 code in libsecp, but not for now ;). 2015-10-26 15:21:01 +00:00			`build = "build.rs"`
			`[build-dependencies]`
			`gcc = "0.3"`

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 = []`
cleanup: remove unused attributes; add `dev` compile feature that'll run clippy 2015-12-20 02:19:45 +00:00			`default = []`
Add fuzztarget feature that replaces crypto with memcpys 2018-03-19 03:16:48 +00:00			`fuzztarget = []`
remove arrayvec dependency; rename PublicKey::serialize_vec 2017-12-19 20:36:46 +00:00
			`[dev-dependencies]`
make `rand` crate optional 2017-12-19 20:49:01 +00:00			`rand = "0.3"`
Update Travis to use travis-cargo 2015-07-28 17:38:01 +00:00
Change rand crate to crates.io version 2015-03-25 23:57:16 +00:00			`[dependencies]`
Increase libc to 0.2 Annoyingly, this is a major version bump since we expose libc types in the FFI module 2016-10-10 13:12:12 +00:00			`libc = "0.2"`
Change rand crate to crates.io version 2015-03-25 23:57:16 +00:00
make `rand` crate optional 2017-12-19 20:49:01 +00:00			`[dependencies.rand]`
			`version = "0.3"`
			`optional = true`