Overview
Artifact ID: | 9d1e9a3834068af4abf3fee7ed96f387ff99762a |
---|---|
Ticket: | 727af73f467a64be0d0bbbcf46c513062a9e4704
ssl: on "pull -R repo", gets ssl certificate again, asks to accept a/y/N |
User & Date: | ben 2011-06-20 07:12:46 |
Changes
- Appended to comment:
<hr /><i>ben added on 2011-06-20 07:12:46 UTC:</i><br /> The ben-testing branch (which includes a competing implementation of SSL client and server certificate management) has an extra ssl-ca-location setting. This calls SSL_CTX_load_verify_locations(). I'm not entirely convinced that fossil should be doing any certificate management. At least, not the way it's doing it now. Perhaps storing the fingerprint of the certificate, rather than the certificate itself, might be the way to go.