@as1 FYI, the only supported way to launch Splunk's embedded Python interpreter is with:
$ splunk cmd python3
The reason for this: Splunk Enterprise's embedded Python interpreter is built against other libraries (like OpenSSL) in Splunk Enterprise, and expects to use those libraries. On Linux, we enforce this by setting LD_LIBRARY_PATH, and that's set through the splunk launcher (you can check what else is set by running `splunk envvars`). Running Python directly outside of the launcher will fail in the way you described, and it's actually been that way for a long while (i.e. it's not new to OpenSSL 3, though the error would have been different across Splunk Enterprise, OpenSSL, and Python versions, as you've noticed). The limitation is true of most everything inside $SPLUNK_HOME/bin and while we're aware "this should just work", starting Python though the splunk launcher is the only thing supported for the time being.
That said, almost always TAs run inside of Splunk's environment, so a TA should never fail this way. Do you mind sharing the precise error you're getting with your TA? This might be better done in a new thread in the forum for TA/appdev support, please create one there, link here, and let's move the discussion there.
... View more