Invalid certificate in ssl_multicert leads to a crash

[vmamidi]

invalid certificate in ssl_multicert.config leads to fatal error. crash is disguised as a vsnprintf seg fault

[bryancall]

This will crash when there is a non-existing file.

[cmcfarlen]

I was not able to reproduce this. I tried a non-existing file, and a corrupted file both at startup and on reload.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. Marking it stale to flag it for further consideration by the community.

[bryancall]

I am closing this as no longer reproducible on current code. When this was first filed, a maintainer could not reproduce a crash with either a non-existing certificate file or a corrupted one, at startup or on reload, and the report has no stack trace or detailed reproduction steps. Since then the ssl_multicert loading path has been substantially reworked, including the migration from ssl_multicert.config to ssl_multicert.yaml (#12755, first released in 11.0.0). Current source validates certificates explicitly: a truncated or corrupted certificate, an unparsable or future notBefore date, and an expired certificate each log an Error and return a negative status (check_server_cert_now in src/iocore/net/SSLUtils.cc), and configuration parse failures now return an error result rather than crashing. If anyone hits a crash loading an invalid certificate on a current release, please reopen with the version, the offending certificate or configuration, and a stack trace.