Could you please be more specific wrt. DRBG organization that in your opinion could impact the UI?
NIST 90Ar1 seems specific enough on what functionality DRBG can provide to users, and it doesn't seem like a very elaborate or rich interface. Why would it change, regardless of what you may need to do with it internally? Regards, Uri Sent from my iPhone > On Aug 29, 2017, at 10:03, Salz, Rich via openssl-dev > <openssl-dev@openssl.org> wrote: > > > dev asap. If there are problems with it we can always revert it before > it makes it into a release. > > Someone on the OMC called that “flip-flopping” and seemed to be against this > kind of thing. > > If we are going to have an additional API, then we should at least see a > draft of the header file first. > > Keep in mind that the current DRBG organization might change, and we don’t > want to lose that freedom. > > > > -- > openssl-dev mailing list > To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
smime.p7s
Description: S/MIME cryptographic signature
-- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
