Seeing "ssl required" on push

Martin Geisler mg at daimi.au.dk
Fri Oct 3 23:35:42 UTC 2008


Andrew Lentvorski <bsder at allcaps.org> writes:

> I saw that there was an earlier complaint about this, but nothing
> seems to have come of it. I'm seeing the same thing with "ssl
> required" on a push. All other operations seem to work fine.
>
> Server is TortoiseHG (0.4.1) on Windows XP. TortoiseHg reports
> Mercurial-1.0.2, Python 2.5.1, PyGtk 2.10.6 and Gtk 2.10.11.
>
> Client attempting the push can either be another TortoiseHg (pushing via 
> Synchronize) or command line Mercurial:
>
> $ hg push http://192.168.205.6:8000/
> pushing to http://192.168.205.6:8000/
> searching for changes
> ssl required

By default, Mercurial will not accept pushes over insecure channels.
Have you tried adding

  [web]
  push_ssl = false

like described here:

  http://www.selenic.com/mercurial/wiki/index.cgi/HgWebDirStepByStep#head-2db756a7f816958aab4c7e7e26e28a9f909fdf99

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multi-Party Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20081004/cec9a7e5/attachment-0001.asc>


More information about the Mercurial mailing list