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.
This release represents a significant redesign of the
secrecy
crate.The most notable change is the generic
Secret<T>
type has been removed: instead useSecretBox<T>
which stores secrets on the heap instead of the stack. Many of the other changes fall out of this
change and things which were previously type aliases of
Secret<T>
are now type aliases ofSecretBox<T>
.This unfortunately means this crate no longer has support for "heapless"
no_std
targets. We don'thave a good solution for these targets, which was a motivation for this change in the first place.
Added
SecretBox::{init_with, try_init_with}
(#1212)SecretBox::init_with_mut
(#1213)?Sized
bounds forSecretBox
(#1213)SecretSlice<T>
(#1214)Changed
SecretBox<T>
is now a newtype rather than a type alias of `Secret<Box> (#1140)SecretString
is now a type alias forSecretBox<str>
(#1213)serde
default features (#1194)Removed
alloc
feature: now a hard dependency (#1140)bytes
crate integration: no replacement (#1140)DebugSecret
trait: no replacement (#1140)Secret<T>
: useSecretBox<T>
instead (#1140)