Neil Horman

@h-vetinari for the purposes of better tracking, can you restate what the concern and proposed solution is here?

@paulidale @slontis @levitte comments here? I'm feeling like this should be closed, so I'm marking inactive, please comment if you want to resurrect it

I'm hesitant to make a change here, given the errata wasn't acted upon, but in the interim, can you confirm that this patch resolves the problem: ``` diff --git a/providers/implementations/kdfs/scrypt.c...

thats...wierd. The default maxmem bytes are 1025*1024^2 Are you passing a OSSL_KDF_PARAM_SCRYPT_MAXMEM param when you do the derivation? what value are you setting there? Thats the only way I could...

I see the problem When we decrypt the key file, openssl identifies the password based encryption scheme by the key encoded nid (scrypt), but passes 0 as the maxmem parameter,...

@paulidale @mattcaswell @t8m @levitte Can I ask you to comment on item 1 above? There is an errata for RFC 7914 here: https://www.rfc-editor.org/errata/rfc7914 which was reported, in which it was...

@kroeckx thats why I suggested a run time check, not a compile time check. We certainly can't determine a valid memory limit at build time, that would be no better...

yes, this is about a KDF that contains settings, the problem is that the settings get set in certain cases as part of a larger operation (in this case PKCS5...

ACK, thanks @paulidale @randombit do you think you can try add a configuration option?

@randombit @paulidale @levitte @kroeckx thank you @randombit as I read it the forward action here is as follows: - [ ] Remove the N check as per the errata (feel...