What does the most recent update to node:18.12.1-alpine do?

[sead-asurion]

We started getting the below errors in our application today after we pulled the node:18.12.1-alpine image (our CI/CD pipeline always pulls the latest from Docker Hub). Can you help me understand what changed in the image, and why the version number didn't change?

/app/dist/index.js:48
                throw new Error(`Failed to read keystore: ${error}`);
                      ^
Error: Failed to read keystore: Error: Invalid openssl exit code: 1
% openssl pkcs12 -in /tmp/3ffc206aa12c0d79853b4155ded1fe46b2e3ef4b -passin file:/tmp/7966b4b3c3d9a27480323cd39435bbea45151f98 -nodes
Error outputting keys and certificates
48AB1740337F0000:error:0308010C:digital envelope routines:inner_evp_generic_fetch:unsupported:crypto/evp/evp_fetch.c:373:Global default library context, Algorithm (RC2-40-CBC : 0), Properties ()

Thanks,

[ttshivers]

Does it work if you add the -legacy option to openssl pkcs12?
See openssl/openssl#12840

nodejs recently updated the latest alpine version to alpine3.17 which has openssl3 as of #1813

[yosifkit]

To add to this, you could alternatively switch to the node:18.12.1-alpine3.16 tag to stay on Alpine 3.16 to get things working as-is.

[sead-asurion]

We use the PEM library for NodeJS to read the keystore. This library uses the openssl command underneath. It doesn't look like PEM supports passing the legacy parameter. We will look into alternate libraries or regenerating the PKCS12 files.