On 7/5/07, Dan Fandrich <dan_at_coneharvesters.com> wrote:
> On Thu, Jul 05, 2007 at 03:14:28PM -0700, Alan Ezust wrote:
> > Here is a strange thing: if I apt-get update over http:// and then
> > switch to https:// in my /etc/sources, apt-get upgrade works fine
> > (because the package list is up to date). That is, apt-get install
> > over https can get the packages that it needs and install them. The
> > errors I am experiencing are specific to apt-get update, not upgrade.
> > Why would it work when it's getting the debs but not when it is
> > downloading the package list?
>
> Could it be that apt-get is actually always ignoring your certificates,
> but is setting CURLOPT_SSL_VERIFYHOST in one case but clearing it in
> another so that the transfer works in that one case regardless?

I'm not sure I understand what you mean here. But that brings me to
another question: Since libcurl is being used by apt, how do I change
the curl runtime options used by apt?

I see mention of a .curlrc file that is used by the command line tool.
But is that used by libcurl (i.e. all software built on top of
libcurl) or just the command line tool?
Received on 2007-07-06