![]() ![]() To get the latest release, check out this article: Release notes for QuickBooks Desktop for Mac 2019. Yes, QuickBooks Desktop for Mac 2019 R13 and later versions work well with macOS 12 Monterey. It appears that it is just not applying the "Custom TLS certificates" setting.Hello, here to provide some information on what you can do in case you lose or delete your QuickBooks Desktop for Mac after updating your operating system. I have also tried using a comma separated list to the pem files, but to no avail. In the settings I then pointed "Custom TLS certificates" to the location on my computer c:\certs that houses both certificates. (yes i know that they are technically the same file contents, but I used openssl just to be certain) I open my webdav url in a browser and export both crt, cer certificates in the chain to a location on my computer, Then convert them to public pem files, because that is what it appears to handle. I am definitely MiTM my connection due to enterprise requirements and I am familiar with this process. While some users might be having issues due to Mitm or self signed certs out of ignorance. I have installed the certificate for the pri… ![]() I have installed the certificate for the private CA in Thunderbird and can sync from Thunderbird to CALDAV and CARDDAV over HTTPS without problem (both Windows and Linux). I have installed the certificate for the private CA in Firefox and can connect to NextCloud over HTTPS from Firefox without problem (both Windows and Linux). The NextCloud server has a TLS certificate signed by a private CA. I am syncing Joplin with a private NextCloud instance. New, TLSv1.2, Cipher is ECDHE-RSA-AES128-GCM-SHA256ĭesktop: Can't get "Custom TLS Certificates" to work Support SSL handshake has read 3206 bytes and written 418 bytes ![]() Issuer=C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 I:O = Digital Signature Trust Co., CN = DST Root CA X3 I:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3ġ s:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 Or $ echo -n | openssl s_client -connect :443ĭepth=2 O = Digital Signature Trust Co., CN = DST Root CA X3ĭepth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 New, TLSv1.2, Cipher is ECDHE-RSA-CHACHA20-POLY1305 SSL handshake has read 3943 bytes and written 419 bytes Issuer=C = US, O = DigiCert Inc, OU = CN = DigiCert SHA2 High Assurance Server CA Subject=C = US, ST = California, L = San Francisco, O = "Dropbox, Inc", OU = Dropbox Ops, CN = I:C = US, O = DigiCert Inc, OU = CN = DigiCert High Assurance EV Root CA I:C = US, O = DigiCert Inc, OU = CN = DigiCert SHA2 High Assurance Server CAġ s:C = US, O = DigiCert Inc, OU = CN = DigiCert SHA2 High Assurance Server CA $ echo -n | openssl s_client -connect :443ĭepth=2 C = US, O = DigiCert Inc, OU = CN = DigiCert High Assurance EV Root CAĭepth=1 C = US, O = DigiCert Inc, OU = CN = DigiCert SHA2 High Assurance Server CAĭepth=0 C = US, ST = California, L = San Francisco, O = "Dropbox, Inc", OU = Dropbox Ops, CN = Ġ s:C = US, ST = California, L = San Francisco, O = "Dropbox, Inc", OU = Dropbox Ops, CN = You can see the whole certificate chain with this, think of it like tracert for certs. You can also test this yourself with openssl. If you examine your browser or OS certificate store, you will most likely find a custom root cert so your browsers don’t throw an error on every https connection. Lots of places use a proxy (like a Barracuda or various cisco appliances) to intercept https traffic so they have visibility into employee usage and/or for data exfil protection, etc… For brevity in the reply, see, e.g. This is common on business-issued machines. ![]()
0 Comments
Leave a Reply. |