Tony Arcieri
Tony Arcieri
As a general rule we tend to put together changelogs with stable releases, not prereleases. That's something we could potentially reconsider.
As discussed in #1713, the encryption API can also wrap up prepending the random nonce to the message, as is customary.
I opened this up for discussion primarily, and also reserved the `kdf` crate name with the minimal proposed API. I think we probably need a lot more traits than this,...
Another important question: output size limits and fallibility. Should we have a `try_derive`/`try_expand` and an `Error` type? How about a trait with an associated constant or typenum type that defines...
@daxpedda I think it would be good to eventually support password-based KDFs. I think they wind up having a very similar API to other KDFs, to the point it might...
Can make another attempt after #2096
4MB seems pretty large for a default buffer size. 8-16kB are exceedingly common as HTTP buffer sizes in other libraries, chosen to be larger than the underlying MTU. Perhaps the...
> As above, whatever we end up doing to `encrypt_in_place`, it would be ideal if we could also have an in-place encryption method that foregoes specialist types in exchange for...
I would really prefer to initially focus exclusively on adapting the detached APIs to use `InOutBuf`, rather than making any simultaneous changes to the in-place APIs, and if we want...
> Finally, about abstracting over prefix versus postfix tags in a high-level API. I think the easiest way to support this will be to provide only slice-to-Buffer encrypt API, i.e....