milksad
/
rust-secp256k1-unsafe-fast
14
0
Fork 0
Code Issues Pull Requests Activity
rust-secp256k1-unsafe-fast/Cargo.toml

44 lines
1.1 KiB
TOML
Raw Normal View History

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.12.1
2019-01-15 16:32:55 +00:00
version = "0.12.1"
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/"
Use latest version at docs.rs
2018-07-09 12:13:13 +00:00
documentation = "https://docs.rs/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"
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"
improve documentation
2018-07-31 15:55:58 +00:00
# Should make docs.rs show all functions, even those behind non-default features
[package.metadata.docs.rs]
attempt to fix docs.rs docs
2018-09-04 14:28:15 +00:00
features = [ "rand", "serde" ]
all-features = true
improve documentation
2018-07-31 15:55:58 +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-dependencies]
Fix cc dep as the rust ecosystem is terrible
2018-12-19 20:12:09 +00:00
cc = "=1.0.26"
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
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]
update `rand` to 0.4
2018-07-30 03:03:20 +00:00
rand = "0.4"
add feature-gated serde 1.0 support for Signature, SecretKey, PublicKey
2018-07-25 13:57:36 +00:00
serde_test = "1.0"
Update Travis to use travis-cargo
2015-07-28 17:38:01 +00:00
make `rand` crate optional
2017-12-19 20:49:01 +00:00
[dependencies.rand]
update `rand` to 0.4
2018-07-30 03:03:20 +00:00
version = "0.4"
make `rand` crate optional
2017-12-19 20:49:01 +00:00
optional = true
add feature-gated serde 1.0 support for Signature, SecretKey, PublicKey
2018-07-25 13:57:36 +00:00
[dependencies.serde]
version = "1.0"
optional = true