Tony Arcieri
Tony Arcieri
It could potentially use a similar technique to the `aes-gcm` crate, which is generic around nonce sizes: https://docs.rs/aes-gcm/latest/aes_gcm/struct.AesGcm.html
Re: RFC5116, it was the original design impetus for the `aead` crate
If you really need a nonce whose length varies at runtime, I’d suggest building on top of the core `Siv` type: https://docs.rs/aes-siv/latest/aes_siv/siv/struct.Siv.html See the `SivAead` type for how the AEAD...
Whoops, should probably leave this open to track potential support for type-level nonce size control
You might mention this issue on that thread as a heads up, i.e. "There's an open issue to file a security advisory for this"
Seems like a lot of duplication between the ARMv8 and ARMv9 backends. Perhaps you could consolidate them? Maybe a module structure like: - `arm` - `v8` - `v9` ...would make...
@silvanshade would you have interest in reopening this?
Here's an experimental crate which implements the idea: https://github.com/dsprenkels/eraser Ideally it would be nice to have first-class compiler support for this sort of thing instead.
Yeah, need to look into that
The next releases will be v0.14 and the docs should build there. If there's legitimate interest I can cut some prereleases.