[pull] master from RustCrypto:master #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dingelish
force-pushed
the
master
branch
2 times, most recently
from
bdfc1ca to
6447161
Compare
Factors apart the detached methods of `AeadInPlace` into a separate `AeadInPlaceDetached` trait, which itself can now more easily be further refactored (by adding e.g. `inout` support). Also adds a `PostfixTagged` trait which is used to gate the blanket impls.
Depends: - zkcrypto/ff#126 - zkcrypto/ff#127 This is to provide an `ecdsa::SigningKey::try_from_rng` API (RustCrypto/signatures#915)
New trait for customized hash function with variable output `CtVariableCoreWrapper` like Blake2 to implement the `CustomizedInit` trait.
This change automates Cargo.lock updates.
This is auto-populated to point at docs.rs
Encourages the use of these traits for initializing decapsulators that impl the `Decapsulate` type. (This is effectively #2056 without the supertrait bound)
Access to typenum constants is needed to impl `KeySizeUser`
Otherwise there's no way to generically access one from the other
Replaces usages of `OsRng` with `getrandom`, and `OsError` with `getrandom::Error`. In `rand_core` v0.10 prereleases, `OsRng` has been moved to the `rand` crate (at least for now). The `rand` crate also depends on `chacha20`, so if we were to depend on `rand` it would create a circular dependency. We can avoid this circular dependency by using `getrandom` directly. By changing the feature name back to `getrandom`, it also matches the existing feature name in stable releases, which is one less thing people need to change in updates. Since `aead` was consuming `OsRng` via `crypto-common`, the latter has been changed to re-export `getrandom`. See also: #1379, #1746, #2063
Includes update to `rand_core` v0.10.0 prereleases
Includes update to `rand_core` v0.10.0 prereleases
This notably switches to `EagerHash` for the digest bound
The change forbids seeking to the last keystream block and its application. Additionally, unchecked methods added as an escape hatch.
Adds support for generating `SecretKey` and `NonZeroScalar` using the system's cryptographically secure random number generator. Notably this renames the former `SecretKey::random` and `NonZeroScalar::random` methods to `SecretKey::generate` and `NonZeroScalar::generate`, which take no parameters and are infallible. This avoids the need for the user to import an `OsRng` type, or worry about the generation failing (which it won't on most notable modern OSes). If a user still wants to handle RNG errors, the `try_from_rng` method still exists, and they can pass `OsRng` if they'd like.
Has people use either the `generate` or `try_from_rng` methods instead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )