SSL and certificate validation¶
All SSL configuration is done per-storage.
Pinning by fingerprint¶
To pin the certificate by fingerprint:
[storage foo] type = "caldav" ... verify_fingerprint = "94:FD:7A:CB:50:75:A4:69:82:0A:F8:23:DF:07:FC:69:3E:CD:90:CA"
SHA256-Fingerprints can be used. CA validation is disabled when pinning a fingerprint.
You can use the following command for obtaining a SHA-1 fingerprint:
echo -n | openssl s_client -connect unterwaditzer.net:443 | openssl x509 -noout -fingerprint
However, please consider using Let’s Encrypt such that you can forget about all of that. It is easier to deploy a free certificate from them than configuring all of your clients to accept the self-signed certificate.
Custom root CAs¶
To point vdirsyncer to a custom set of root CAs:
[storage foo] type = "caldav" ... verify = "/path/to/cert.pem"
Vdirsyncer uses the aiohttp library, which uses the default `ssl.SSLContext https://docs.python.org/3/library/ssl.html#ssl.SSLContext`_ by default.
There are cases where certificate validation fails even though you can access
the server fine through e.g. your browser. This usually indicates that your
python or the
aiohttp or library is somehow broken. In
such cases, it makes sense to explicitly set
verify_fingerprint as shown above.
Client certificates may be specified with the
auth_cert parameter. If the
key and certificate are stored in the same file, it may be a string:
[storage foo] type = "caldav" ... auth_cert = "/path/to/certificate.pem"
If the key and certificate are separate, a list may be used:
[storage foo] type = "caldav" ... auth_cert = ["/path/to/certificate.crt", "/path/to/key.key"]