Hello, So, rather than just grep:ing for something along the line of "cert" and then extrapolating the rest, I actually read the code this time. I figured out why no one is explaining to me how to specify which client certificate to use when connecting with https: Because fossil doesn't support it yet. :)
Our development server only allows fully verified certificate chains when connecting to it (with the exception of ssh); I added support for specifying a certificate and key file to my local fossil copy, and now I can properly access our repositories through https (via apache and cgi). However, it seems appropriate to implement this properly so that everyone can benefit from it. Is anyone working on this already? If not, is this a feature which we'd like in the official fossil distribution? Please let me know about any particular wish-list items you may have with regards to client key/certificate support. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
