More specifically, even if I change the main executable to an arm binary, this poisoning issue still exists. We have an app that will work fine on a clean install of MacOS, that does not work on the target system. We are trying to deploy a fix to this issue, and right now the only solution I can pass along is "reinstall MacOS".

Sorry if this a duplicate, my original comment disappeared. This is for a github action so it is headless. I need to add a ssl cert to test our product. I am running as root because as the documentation for SecTrustSettingsSetTrustSettings says "the user is prompted with an alert panel asking for an administrator’s name and password unless the calling process is running as root".

I am running as root because I am trying to reproduce the behavior described in the documentation for SecTrustSettingsSetTrustSettings "the user is prompted with an alert panel asking for an administrator’s name and password unless the calling process is running as root". I am trying to trust a ssl cert for a github action, and it is headless.