You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of hardcoding md5 hash for the temporary name, consider moving to something higher like sha1 at a minimum or check for FIPs compliance and make it variable. I tested by moving the function createhash() call to sha1 and it proceeds fine.
The text was updated successfully, but these errors were encountered:
This is fixed by 22dd875, which was landed in lieu of #7 because of my poor reading comprehension skills (sorry again, @stefanmb). [email protected] (currently npm@next) includes the fixed version of write-file-atomic, and should work with FIPS builds of Node.js. Thanks for the heads up!
When NodeJS is compiled for FIPS-compliance, write-file-atomic actually breaks NPM.
When NPM attempts to write the local cache file .cache.json using writeFile from the library, it throws the following:
fips_md.c(146): OpenSSL internal error, assertion failed: Digest update previous FIPS forbidden algorithm error ignored
Aborted
Instead of hardcoding md5 hash for the temporary name, consider moving to something higher like sha1 at a minimum or check for FIPs compliance and make it variable. I tested by moving the function createhash() call to sha1 and it proceeds fine.
The text was updated successfully, but these errors were encountered: