Neil Horman

no response, marking as inactive, to be closed at the end of 3.4 dev barring further input

looks like maybe you need to modify the appropriate ci builds such that they compile with a higher SCRYPT_MAX_MEMORY limit defined on the command line?

hmm, @davidben you're right. I took the pkcs8 key in #24650, and ran it through gdb: ``` tarting program: /home/nhorman/git/openssl/apps/openssl pkcs8 -inform PEM -in /home/nhorman/key.pem [Thread debugging using libthread_db enabled]...

though it does beg the question about what (if anything) to do with that unaddressed errata

see https://github.com/openssl/openssl/pull/24450 We're actively working on creating a windows installer which enables registry keys for both the install time defaults as well as run time environment variables to override them,...

by windows installer, I am specifically referring to this installer: https://github.com/openssl/installer The pr mentioned above works with the installer in that it references registry keys created (or soon to be...

because there is no guarantee that the installer will place the directory paths below the installer location. An administrator may select to place OPENSSLDIR in a common area, so that...

Ostensibly the use of registry keys under HKEY_LOCAL_MACHINE prevents that as well, as those registry keys should be write protected for any non-administrative user.

we fall back to the build time defines for OPENSSLDIR/ENGINESDIR/MODULESDIR

Not without application developers who include openssl as a component changing their install procedure, no. But that seems ok. I don't want to go hardcoding a policy into openssl that...