rust-secp256k1-unsafe-fast/Cargo.toml

[package]
name = "secp256k1"
version = "0.21.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 wrapper library for Pieter Wuille's `libsecp256k1`. Implements ECDSA and BIP 340 signatures 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", "bitcoin_hashes", "recovery", "global-context" ]
rustdoc-args = ["--cfg", "docsrs"]

[features]
unstable = ["recovery", "rand-std"]
default = ["std"]
std = ["secp256k1-sys/std"]
# allow use of Secp256k1::new and related API that requires an allocator
alloc = []
rand-std = ["rand/std"]
recovery = ["secp256k1-sys/recovery"]
lowmemory = ["secp256k1-sys/lowmemory"]
global-context = ["std"]
# disable re-randomization of the global context, which provides some
# defense-in-depth against sidechannel attacks. You should only use
# this feature if you expect the `rand` crate's thread_rng to panic.
# (If you are sure the `rand-std` feature will not be enabled, e.g.
# if you are doing a no-std build, then this feature does nothing
# and is not necessary.)
global-context-less-secure = []

[dependencies]
secp256k1-sys = { version = "0.4.2", default-features = false, path = "./secp256k1-sys" }
bitcoin_hashes = { version = "0.10", optional = true }
rand = { version = "0.6", default-features = false, optional = true }
serde = { version = "1.0", default-features = false, optional = true }


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

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


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

[[example]]
name = "sign_verify"
required-features = ["std"]

[[example]]
name = "generate_keys"
required-features = ["std", "rand-std"]

[workspace]
members = ["secp256k1-sys"]
exclude = ["no_std_test"]
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"`
Release 0.21.2 2022-01-06 17:17:45 +00:00			`version = "0.21.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/"`
Adding KeyPair::serialize_sec. Closes #298 2021-06-19 09:06:27 +00:00			description = "Rust wrapper library for Pieter Wuille's `libsecp256k1`. Implements ECDSA and BIP 340 signatures for the SECG elliptic curve group secp256k1 and related utilities."
Update Cargo.toml for crates.io metadata; this marks the "official" 0.1.0 release 2015-05-04 15:26:45 +00:00			`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]`
Added missing features to docs.rs config These features were previously forgotten and without them the docs.rs doc is not that great. :( 2022-01-07 00:12:41 +00:00			`features = [ "rand", "rand-std", "serde", "bitcoin_hashes", "recovery", "global-context" ]`
Documented features This documents the Cargo features making sure docs.rs shows warning for feature-gated items. They are also explicitly spelled out in the crate documentation. 2022-01-04 15:55:01 +00:00			`rustdoc-args = ["--cfg", "docsrs"]`
improve documentation 2018-07-31 15:55:58 +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"]`
New alloc feature Allows use of `Secp256k1::new` and related API if an allocator is available 2021-05-17 12:37:36 +00:00			`# allow use of Secp256k1::new and related API that requires an allocator`
			`alloc = []`
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"]`
			`lowmemory = ["secp256k1-sys/lowmemory"]`
Remove feature global-context-less-secure Instead of providing a mechanism for users to opt out of randomization we can just feature gate the call site i.e., opportunistically randomize the global context on creation if `rand-std` feature is enabled. 2022-02-01 04:43:46 +00:00			`global-context = ["std"]`
restore `global-context-less-secure` feature 2022-02-16 23:46:52 +00:00			`# disable re-randomization of the global context, which provides some`
			`# defense-in-depth against sidechannel attacks. You should only use`
			# this feature if you expect the `rand` crate's thread_rng to panic.
			# (If you are sure the `rand-std` feature will not be enabled, e.g.
			`# if you are doing a no-std build, then this feature does nothing`
			`# and is not necessary.)`
			`global-context-less-secure = []`
Add warnings to Cargo.toml features 2019-10-28 21:21:47 +00:00
Add secp256k1-sys 2019-10-21 12:15:19 +00:00			`[dependencies]`
release secp256k1-sys 0.4.2; make new `ZERO` type publically accessible 2022-01-05 15:56:49 +00:00			`secp256k1-sys = { version = "0.4.2", default-features = false, path = "./secp256k1-sys" }`
Bump bitcoin_hashes to version 0.10 Requires for interoperability of the `ThirtyTwoByteHash` trait with rust-bitcoin. 2021-09-08 05:21:39 +00:00			`bitcoin_hashes = { version = "0.10", optional = true }`
Sort Cargo.toml files 2020-08-27 19:58:00 +00:00			`rand = { version = "0.6", default-features = false, optional = true }`
			`serde = { version = "1.0", default-features = false, optional = true }`

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"`
Bump bitcoin_hashes to version 0.10 Requires for interoperability of the `ThirtyTwoByteHash` trait with rust-bitcoin. 2021-09-08 05:21:39 +00:00			`bitcoin_hashes = "0.10"`
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"] }`

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"`
Be explicit about example feature requirements The examples depend on having the "std" feature [1]. In preparation for being able to run tests with `--no-default-features` add the "std" feature as a requirement for all three examples. While we are at it use the correct rand feature requirement: `rand-std`. [1] Technically we only need "alloc" but "alloc" is not working with Rust 1.29 currently so just use "std". 2022-02-01 03:59:29 +00:00			`required-features = ["std", "recovery"]`
Aded an example for recoverable signatures and recovering the pubkey 2019-10-28 20:10:31 +00:00
Added an example for signing and verification 2019-10-28 20:09:59 +00:00			`[[example]]`
			`name = "sign_verify"`
Be explicit about example feature requirements The examples depend on having the "std" feature [1]. In preparation for being able to run tests with `--no-default-features` add the "std" feature as a requirement for all three examples. While we are at it use the correct rand feature requirement: `rand-std`. [1] Technically we only need "alloc" but "alloc" is not working with Rust 1.29 currently so just use "std". 2022-02-01 03:59:29 +00:00			`required-features = ["std"]`
Added an example for signing and verification 2019-10-28 20:09:59 +00:00
Added an example for generating keys using OsRng 2019-10-28 20:09:18 +00:00			`[[example]]`
			`name = "generate_keys"`
Be explicit about example feature requirements The examples depend on having the "std" feature [1]. In preparation for being able to run tests with `--no-default-features` add the "std" feature as a requirement for all three examples. While we are at it use the correct rand feature requirement: `rand-std`. [1] Technically we only need "alloc" but "alloc" is not working with Rust 1.29 currently so just use "std". 2022-02-01 03:59:29 +00:00			`required-features = ["std", "rand-std"]`
Make test.sh test and build secp256k1-sys 2020-12-18 12:08:52 +00:00
			`[workspace]`
			`members = ["secp256k1-sys"]`
bump version to 0.20.1 2021-01-11 19:15:10 +00:00			`exclude = ["no_std_test"]`