Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 27 Nov 2012 10:36:42 +0100
From:      Lars Engels <lars.engels@0x20.net>
To:        Alexander Yerenkow <yerenkow@gmail.com>
Cc:        cpervica@freebsd.org, freebsd-stable@freebsd.org, Luca Ferrari <fluca1978@infinito.it>
Subject:   Re: simple patch for portsnap to use wget
Message-ID:  <20121127093642.GD96846@e-new.0x20.net>
In-Reply-To: <CAPJF9wnoTCjNM76M-=DdC85P75niKH%2Bta0Vk8X7HORGvT=LLcQ@mail.gmail.com>
References:  <CAKoxK%2B5iy2R7=cZp38xKZpTbgFd0aZ3H28tVmPnuPR01w=pO4A@mail.gmail.com> <CAPJF9wnoTCjNM76M-=DdC85P75niKH%2Bta0Vk8X7HORGvT=LLcQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--4X8KWh4JEk7YXJIe
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 27, 2012 at 10:22:09AM +0200, Alexander Yerenkow wrote:
> Do you aware that if wget tries download from https, and there is
> self-signed certificate, then it fails, and ask for --no-check-certificate
> option?
> How do your patch deal in that case?
>=20
> 2012/11/27 Luca Ferrari <fluca1978@infinito.it>
>=20
> > Hi all,
> > I was in trouble for a while because I was using FreeBSD behind an
> > http proxy (a palo alto for what it means) and the portsnap command
> > was unable to handle updates reporting always "file does not exist".
> > After digging I found that the problem was in the phttpget command
> > used internally from portsnap: phttpget is not able to handle an
> > http_proxy variable in the form of http://user:password@proxy:port
> > since the first colon is understood as a port separator and therefore
> > phttpget tries to connect to the host "user" on port
> > "password@proxy:port". Since I did not found much documentation about
> > how to solve the problem, and nobody on the forum was able to point me
> > in any direction (see
> > http://forums.freebsd.org/showthread.php?t=3D28849) I wrote a simple
> > patch to modify portsnap to use wget instead of phttpget.
> > Of course, this means you have to install wget first, and also the
> > laminating of the files to download has slightly changed within
> > portsnap, but I'm using it from several days and updates now and it
> > seems to work well.
> > Now the question is: should this patch, or better the idea of using
> > wget or another alike substitute to phttpget, be integrated into the
> > system?
> > I've tested it on FreeBSD-9-STABLE.
> >

This should really be fixed in portsnap / phttpget itself. (cpervica
CC'ed).
wget is not part of the base system.

--4X8KWh4JEk7YXJIe
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (FreeBSD)

iEYEARECAAYFAlC0iaoACgkQKc512sD3afh27wCfcR5V06n5k/O9iti3L8HGXQV1
BHkAoII9fhuSYgzrq2li3e6g0HqruLbQ
=dICs
-----END PGP SIGNATURE-----

--4X8KWh4JEk7YXJIe--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121127093642.GD96846>