SSL problem with bzr-svn -- blocking problem

[Jelmer Vernooij]

On Fri, 2010-07-02 at 12:17 +0200, Jelmer Vernooij wrote:
> On Fri, 2010-07-02 at 11:12 +0100, Russel Winder wrote:
> > On Fri, 2010-07-02 at 06:01 -0400, John Szakmeister wrote:
> > > On Fri, Jul 2, 2010 at 5:48 AM, Jelmer Vernooij <jelmer at samba.org> wrote:
> > > [snip]
> > > > This is caused by pycurl being installed on your system. You can work
> > > > around it by forcing the use of urllib, using https+urllib:// as the
> > > > scheme in the URL.
> > > 
> > > Or use the attached plugin to disable pycurl (it re-register's urllib
> > > ahead of pycurl so you don't have to remember to do the trick above).
> > Alternatively this code should be in bzr-svn so the user never has to
> > suffer these implementation details.
> This behaviour is in no way specific to bzr-svn, you would have the same
> issue if you were to access a normal Bazaar branch over a HTTPS
> connection with a server that was using a self-signed certificate. 
> 
> I can see the argument for defaulting to urllib (also the argument for
> defaulting to pycurl, as you probably want to see when you're talking to
> a server with an untrusted cert.), but this change should be discussed
> in the context of bzr, not bzr-svn. 

> See also the following bugs on Launchpad:
https://bugs.edge.launchpad.net/bzr/+bug/125055
https://bugs.edge.launchpad.net/bzr/+bug/82086


> > I could go into a rant about making inappropriate assumptions and about
> > forcing users to think about implementation details they know nothing
> > about, but I am feeling mellow, so I'll go for subtlety. ;-)
> :-)