Open cerebrate opened 3 years ago
I can work around this temporarily by patching _oprint/lib/python3.7/site-packages/matrixclient/api.py to include the last line below:
def __init__(self, base_url, token=None, identity=None, default_429_wait_ms=5000):
self.base_url = base_url
self.token = token
self.identity = identity
self.txn_id = 0
self.validate_cert = True
self.session = Session()
self.default_429_wait_ms = default_429_wait_ms
self.session.verify = '/etc/ssl/certs/ca-certificates.crt'
but that's hardly a fix. Since the problem is with matrix_client and not with Octoslack, I should report this over there, but since on the other hand matrix_client is almost-but-not-quite deprecated in favor of matrix-nio and they're not taking bug fixes or feature requests at this time, I'm leaving it open here.
I have an internal Matrix server which I'd like to use for Octoslack notifications, but I can't connect to the server because it uses a certificate issued by a local (internal) CA rather than a default CA:
I've added the local CA root certificate to the Octoprint host and run
update-ca-certificates
, and running a few manual tests in python with the requests library suggests that python can validate the certificate correctly, at least for a simple requests.get().How can I get this CA cert into/used by Octoslack, or failing that as a workaround, disable SSL verification temporarily?