Hello Mark,
On Mon, Aug 22, 2016 at 11:20:06AM +0100, Mark Hindley wrote:
> Thanks. I am wondering where your HTTPS upstream is configured? What do you 
> have in /etc/apt/sources.list?

root@samd:~# grep -v "^#" /etc/apt/sources.list
deb http://172.16.18.51:9999/debian testing main

Where 172.16.18.51 is the local IP of this machine.

> On Sun, Aug 21, 2016 at 05:03:29PM +0200, Helge Kreutzmann wrote:
> > > Are you trying to use HTTPS for upstream? If so, you will need to set 
> > > curl_ssl_insecure or use the libcurl option to configure CA to verify the 
> > > upstream connection.
> > 
> > Is there some documentation to do this libcurl configuration? I'd
> > rather configure the CA properly, but could not find any docs for
> > this.
> 
> Temporarily try the curl_ssl_insecure option first. If that helps we know we 
> are on the right track. 

Ok, I added:
libcurl = insecure
or
libcurl = curl_ssl_insecure

to /etc/apt-cacher/apt-cacher.conf but, unfortunately this does not
change anything.

> The libcurl option in mentioned in man apt-cacher(8). It should accept 
> anything from curl_easy_setopt(3), which requires the libcurl dev package

I installed libcurl4-doc but the curl_easy_setopt(3) does not specify
anything with INSECURE or insecure, nor did I find anything amongst
the many options under the heading of 
SSL and SECURITY OPTIONS

Could you check?

Thanks!

Greetings

         Helge
-- 
      Dr. Helge Kreutzmann                     deb...@helgefjell.de
           Dipl.-Phys.                   http://www.helgefjell.de/debian.php
        64bit GNU powered                     gpg signed mail preferred
           Help keep free software "libre": http://www.ffii.de/

Attachment: signature.asc
Description: Digital signature

Reply via email to