Date: Tue, 27 Nov 2012 09:49:01 +0100 From: Luca Ferrari <fluca1978@infinito.it> To: freebsd-stable@freebsd.org Subject: Fwd: simple patch for portsnap to use wget Message-ID: <CAKoxK%2B5qivgzMzkOQo7JYOQGAKwyWAf8xfUUR=g5SvpguM2W7Q@mail.gmail.com> In-Reply-To: <CAKoxK%2B5yrsfnMQG5LnJ2%2BFWMH6PDcWmZhKVrKpxkutHpb=MdNA@mail.gmail.com> References: <CAKoxK%2B5iy2R7=cZp38xKZpTbgFd0aZ3H28tVmPnuPR01w=pO4A@mail.gmail.com> <CAPJF9wnoTCjNM76M-=DdC85P75niKH%2Bta0Vk8X7HORGvT=LLcQ@mail.gmail.com> <CAKoxK%2B5yrsfnMQG5LnJ2%2BFWMH6PDcWmZhKVrKpxkutHpb=MdNA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry, back to list. On Tue, Nov 27, 2012 at 9:22 AM, Alexander Yerenkow <yerenkow@gmail.com> 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? It simply does not. Are the usage of ports allowed to provide self-signed certificates over https? However I think it is possible to make an option in portsnap.conf to allow for no-check-certificate option for wget. Luca
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKoxK%2B5qivgzMzkOQo7JYOQGAKwyWAf8xfUUR=g5SvpguM2W7Q>