You saidd Fossil was server via CGI? In that case, the webserver is handling the SSL negotiation. Also, as best I know, Fossil does not handle the server side of SSL, anyway. See:
http://fossil-scm.org/index.html/doc/tip/www/ssl.wiki http://fossil-scm.org/index.html/doc/tip/www/server.wiki On Tue, Oct 15, 2013 at 12:39 PM, j. van den hoff <[email protected] > wrote: > hi, > > a colleague in the US just tried to clone a cgi-served repo via https > (residing in germany) like > > fossil clone https:usrname@server/repos/**somerepo > > and received (contrary to myself) warning messages regarding > > "SSL verification failed: self signed certificate in certificate chain" > etc. > > > as our IT admin explains this probably is caused by the fact that the root > certificate is a german one (from deutsche telekom) and that this is not > known at the site of the colleague in the US. > > the problem is this: the colleague is then prompted whether to accept the > certificate anyway > > "Accept certificate for host {ourserver} (a=always/y/N)" > > which he answered with "y" which leads to > > "server did not reply" > > > when he answered the same question with "a", the clone succeeded. > > question: my understanding is these warnings and the prompting for how to > proceed is done by fossil, right? if so, am I do understand that this is a > fossil problem? should I expect > the "server did not reply" message after answering "y" or is this a bug > (of SSL, of fossil, or whatever)? I'm quite at a loss here. > ______________________________**_________________ > fossil-users mailing list > [email protected].**org <[email protected]> > http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
