RetroSearch Browse

Wed Aug 1 14:19:19 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-August/121208.html

On Wed, 1 Aug 2012 14:12:54 +0200
Antoine Pitrou <solipsis at pitrou.net> wrote:

> On Wed, 01 Aug 2012 05:58:06 +0200
> Jesus Cea <jcea at jcea.es> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > My mercurial clone is <https://hg.jcea.es/cpython-2011/>, and today I
> > can't create a patch from it (in the bug tracker). No explanation in
> > the web interface, but checking the sourcecode of the resulting page,
> > I see a SSL certificate failure.
> > 
> > So, looks like bugs.python.org is now verifying repository certificates.
> > 
> > My certificate is selfsigned and, moreover, it is behind a SNI server,
> > so the certificate python.org is getting is a selfsigned "jcea.es"
> > certificate.
> > 
> > What can I do, beside buying a "real" cert?.
> 
> Why don't you just use a HTTP URL?

Whoops, I hadn't seen the P.S. in your e-mail:

> PS: If I try to use the http version of my repository
> (<http://hg.jcea.es/cpython-2011>), I get an error: "('invalid token',
> 97)".

In this case the issue with the http version should perhaps be figured
out first.

Regards

Antoine.

-- 
Software development and contracting: http://pro.pitrou.net

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-August/121208.html below:

[Python-Dev] HTTPS repositories failing when using selfsigned certs