March 3 2016 10:11 AM, "Adrien Destugues" <pulkomandy@xxxxxxxxxxxxx> wrote:
3 mars 2016 16:53 "Alexander von Gluck IV" <kallisti5@xxxxxxxxxxx> a écrit:
The crypto kit hashing features are complete.
* Is the API desirable?
Anything that avoids app developers to mess with OpenSSL "APIs" directly is
desirable.
* Should this be a post-R1 feature or a pre-R1 feature?
Beta1 must be feature complete for all the features planned in R1. We are
already having enough
trouble getting it out, so, post-R1.
* Should it be merged before the encryption / decryption portions are
defined / complete?
I think it can start as a separate package for now, and if usages takes up,
we can always include
it in the main set of APIs. This leaves you the freedom to change the design
as much as you need.
If you think it should be in trunk, it should go the usual route for new APIs
(ie spend some time
in BPrivate + a static lib) until the API/ABI is stable, with FBC padding and
everything.