Tomáš Mráz
Tomáš Mráz
We will need a CLA submitted to be able to accept this PR, could you please follow the instructions at: https://www.openssl.org/policies/cla.html
> Can anyone some light on why the documentation is not being generated even though the .pod file is clearly in the correct directory? Apparently `check_docs` is failing because of...
Could you please rebase the PR on top of fresh master branch? There are now unfortunately some conflicts to resolve.
> Well, let's say my password is "**secretkey**", onece I apply the API's to get PBKDF2_SHA256 output, then how would I know that the given output is correct? You cannot...
@ckalina I still see some of the comments unaddressed.
@mattcaswell Is it realistic to get this merged before 3.0 beta1? If not, should we lower the stress level and just wait for when the master is opened for 3.1?
> > @mattcaswell Is it realistic to get this merged before 3.0 beta1? If not, should we lower the stress level and just wait for when the master is opened...
> * What about thread support in FIPS? (Currently, the code is not available there.) Well, Argon2 is not targeted at fips module so no problem with that. For now...
It is really up to @openssl/omc to make the decision to spend the project resources on reviewing this PR (and the Argon2 one but that should be much smaller effort)....
> Most of the files are 2021 dated ;) That's no problem as before any release we update copyrights on all the files that were touched.