Tony Arcieri

If one of the existing impls `Zeroize` provides works on them yes. However, if the underlying types can be moved/copied, they will still leave copies in memory.

There is one problem with using the `aead` crate's traits for Snow's purposes right now: [they aren't object safe](https://github.com/RustCrypto/traits/issues/70), but easily could be with some small changes.

@aep are you running into one of these issues, perhaps? https://github.com/rust-lang/cargo/issues/4664 https://github.com/rust-lang/cargo/issues/4866

@aep aah yep, I've run into that a lot with `criterion` specifically. One option is to make a `benches` (or thereabouts) crate and make it part of the same workspace....

@nickray I'm interested in doing something quite similar! (not PIV or that class of token, but trying to encrypt a channel to a USB device) > One way I'd hope...

Note: I made a [`ring-aead`](https://crates.io/crates/ring-aead) crate for using the [`aead::Aead`](https://docs.rs/aead/latest/aead/trait.Aead.html) trait with *ring*'s cipher implementations: https://github.com/RustCrypto/AEADs/tree/master/ring

@jhpratt the author of this RFC @matklad is the author of `once_cell`. It also mentions: > The proposed API is directly copied from `once_cell` crate.

Sorry for showing up late to the party here! Credential design is very much something I'm interested in, and [proposed a feature along these lines at the Bay Area Rust...

Separately, it'd be good to know the plan for how this feature would interact with stateful sessions were they to be implemented: https://github.com/rust-lang/crates.io/issues/2630

Is the data you need cached locally somewhere already, e.g. either in the crates.io index itself (which can be consumed using the [`crates_index` crate](https://docs.rs/crates-index/)), or via the crate file cache...