rust-secp256k1-unsafe-fast/Cargo.toml

[package]

name = "secp256k1"
version = "0.17.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/"
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"
autoexamples = false # Remove when edition 2018 https://github.com/rust-lang/cargo/issues/5330

# Should make docs.rs show all functions, even those behind non-default features
[package.metadata.docs.rs]
features = [ "rand", "rand-std", "serde", "recovery", "endomorphism" ]

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

[features]
unstable = ["recovery", "rand-std"]
default = ["std"]
std = ["secp256k1-sys/std"]
rand-std = ["rand/std"]
recovery = ["secp256k1-sys/recovery"]
endomorphism = ["secp256k1-sys/endomorphism"]
lowmemory = ["secp256k1-sys/lowmemory"]

# Use this feature to not compile the bundled libsecp256k1 C symbols,
# but use external ones. Use this only if you know what you are doing!
external-symbols = ["secp256k1-sys/external-symbols"]

# Do not use this feature! HAZMAT. (meant for Fuzzing only. this is *BROKEN CRYPTOGRAPHY*)
fuzztarget = ["secp256k1-sys/fuzztarget"]

[dependencies]
secp256k1-sys = { version = "0.1.1", default-features = false, path = "./secp256k1-sys" }

[dev-dependencies]
rand = "0.6"
rand_core = "0.4"
serde_test = "1.0"
bitcoin_hashes = "0.7"

[target.wasm32-unknown-unknown.dev-dependencies]
wasm-bindgen-test = "0.3"
rand = { version = "0.6", features = ["wasm-bindgen"] }

[dependencies.rand]
version = "0.6"
optional = true
default-features = false

[dependencies.serde]
version = "1.0"
optional = true
default-features = false

[[example]]
name = "sign_verify_recovery"
required-features = ["recovery"]

[[example]]
name = "sign_verify"

[[example]]
name = "generate_keys"
required-features = ["rand"]
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.17.2 2020-01-09 15:08:39 +00:00			`version = "0.17.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/"`
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"`
Added an example for generating keys using OsRng 2019-10-28 20:09:18 +00:00			`autoexamples = false # Remove when edition 2018 https://github.com/rust-lang/cargo/issues/5330`
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]`
Bump version to 0.16 2019-10-28 20:31:57 +00:00			`features = [ "rand", "rand-std", "serde", "recovery", "endomorphism" ]`
improve documentation 2018-07-31 15:55:58 +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]`
Fix broken benchmarks 2020-03-24 13:20:18 +00:00			`unstable = ["recovery", "rand-std"]`
Replaced std with core, and made std::error::Error optional through feature 2019-02-18 12:30:39 +00:00			`default = ["std"]`
Add secp256k1-sys 2019-10-21 12:15:19 +00:00			`std = ["secp256k1-sys/std"]`
Add a rand-std feature 2019-08-22 00:16:11 +00:00			`rand-std = ["rand/std"]`
Add secp256k1-sys 2019-10-21 12:15:19 +00:00			`recovery = ["secp256k1-sys/recovery"]`
			`endomorphism = ["secp256k1-sys/endomorphism"]`
			`lowmemory = ["secp256k1-sys/lowmemory"]`
Add warnings to Cargo.toml features 2019-10-28 21:21:47 +00:00
Add external-symbols feature to support external libsecp This feature disables using the bundles sources and will link into existing libsecp256k1 symbols. 2019-10-29 11:19:53 +00:00			`# Use this feature to not compile the bundled libsecp256k1 C symbols,`
			`# but use external ones. Use this only if you know what you are doing!`
			`external-symbols = ["secp256k1-sys/external-symbols"]`

Add warnings to Cargo.toml features 2019-10-28 21:21:47 +00:00			`# Do not use this feature! HAZMAT. (meant for Fuzzing only. this is BROKEN CRYPTOGRAPHY)`
Add secp256k1-sys 2019-10-21 12:15:19 +00:00			`fuzztarget = ["secp256k1-sys/fuzztarget"]`

			`[dependencies]`
Bump to v0.17.1 2019-12-11 17:50:23 +00:00			`secp256k1-sys = { version = "0.1.1", default-features = false, path = "./secp256k1-sys" }`
remove arrayvec dependency; rename PublicKey::serialize_vec 2017-12-19 20:36:46 +00:00
			`[dev-dependencies]`
Libraries versions 2019-11-20 14:44:53 +00:00			`rand = "0.6"`
			`rand_core = "0.4"`
			`serde_test = "1.0"`
			`bitcoin_hashes = "0.7"`
Update Travis to use travis-cargo 2015-07-28 17:38:01 +00:00
Re-support WASM via simple stub headers libsecp256k1 really only barely uses libc at all, and in practice, things like memcpy/memcmp get optimized into something other than a libc call. Thus, if we provide simple stub headers, things seem to work with wasm-pack just fine. 2020-04-16 17:07:14 +00:00			`[target.wasm32-unknown-unknown.dev-dependencies]`
			`wasm-bindgen-test = "0.3"`
			`rand = { version = "0.6", features = ["wasm-bindgen"] }`

make `rand` crate optional 2017-12-19 20:49:01 +00:00			`[dependencies.rand]`
Bumps rand to 0.6.3 & associated updates 2019-01-11 20:57:34 +00:00			`version = "0.6"`
make `rand` crate optional 2017-12-19 20:49:01 +00:00			`optional = true`
Replaced std with core, and made std::error::Error optional through feature 2019-02-18 12:30:39 +00:00			`default-features = false`
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`
Replaced std with core, and made std::error::Error optional through feature 2019-02-18 12:30:39 +00:00			`default-features = false`
Added an example for generating keys using OsRng 2019-10-28 20:09:18 +00:00
Aded an example for recoverable signatures and recovering the pubkey 2019-10-28 20:10:31 +00:00			`[[example]]`
			`name = "sign_verify_recovery"`
			`required-features = ["recovery"]`

Added an example for signing and verification 2019-10-28 20:09:59 +00:00			`[[example]]`
			`name = "sign_verify"`

Added an example for generating keys using OsRng 2019-10-28 20:09:18 +00:00			`[[example]]`
			`name = "generate_keys"`
Libraries. 2019-11-18 01:04:11 +00:00			`required-features = ["rand"]`