On Mon, Oct 28, 2013 at 8:39 AM, Jan Nijtmans <jan.nijtm...@gmail.com>wrote:
> 2013/10/28 Jan Nijtmans <jan.nijtm...@gmail.com>: > > >fossil sync https://jan.nijtmans:*********@ > www.fossil-scm.org/fossil > > via proxy: http://130.139.104.40:8080 > ..... > > So, if this little thing could be fixed as well, it would be perfect! > > Follow-up: If I do the same without specifying the password in the url: > >fossil sync https://jan.nijtm...@www.fossil.org/fossil > password for jan.nijtmans: ********* > remember password (Y/n)? Y > via proxy: http://130.139.104.40:8080 > > Conclusion: your branch works fine as long as the password is > not taken from the (https) url. > I assume you repeated the test with a fresh repository since you had previously allowed Fossil to always accept the cert. In any case, the cert displayed did not look like a self-signed cert, so I would be concerned that the incorrect cert was displayed. >From the question/response dialog, I assume that Fossil was what rejected the cert, so I have to wonder why? Beyond, I think there should be a choice between "yes, just this time" and "always now and all future times", specifically, "yes for the duration of this command", since Fossil often performs multiple HTTP/HTTPS exchanges during a pull/push/sync.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
