You are not logged in.
After the following upgrade:
[2018-09-14 15:54] [ALPM] upgraded openssl (1.1.0.i-1 -> 1.1.1-1)
Offlineimap stopped being able to connect to imap.gmail.com, with complaints about the SSL certificate. I tried installing isync and got:
SSL error connecting imap.gmail.com (64.233.166.108:993): self signed certificate
After downgrading the openssl package back down to 1.1.0.i-1 I was able to connect again.
Is it a security risk if I keep the downgraded openssl? Is this something Google needs to update, or does the new openssl package need some kind of fix?
Last edited by woodape (2018-09-16 05:55:16)
Offline
https://bugs.archlinux.org/task/60059
offlineimap does not support SNI which is required by gmail for TLS 1.3
Edit:
isync same issue should be fixed by https://sourceforge.net/p/isync/isync/c … 5790c05d27
Last edited by loqs (2018-09-15 11:05:53)
Offline
Another workaround is to replace sslcacertfile with cert_fingerprint.
Offline
I worked around this for now by adding
SSLVersions TLSv1.1
to my .mbsyncrc for each IMAP account.
Edit: I keep using Markdown syntax!
Last edited by firecat53 (2018-09-15 19:26:49)
Offline
I worked around this for now by adding
SSLVersions TLSv1.1
to my .mbsyncrc for each IMAP account.
This seems to work for me. Marking it solved. Thanks for the info everyone!
Offline
IMO, a better option is to apply loqs' patch (on the bugtracker).
Offline
After installing isync and giving it a test-run, I think I actually like it better than offlineimap - it's a little easier on my CPU. But if I change my mind soon, and the patch isn't applied in the official package, I'll apply it myself. Thanks for the help, and thanks @loqs for doing the patch work!
Offline