simple patch for portsnap to use wget

Alexander Yerenkow yerenkow at
Tue Nov 27 08:22:23 UTC 2012

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
How do your patch deal in that case?

2012/11/27 Luca Ferrari <fluca1978 at>

> 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 at 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
> 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.
> Regards,
> Luca
> _______________________________________________
> freebsd-stable at mailing list
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at"

Alexander Yerenkow

More information about the freebsd-stable mailing list