From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-02
Date: Mon, 05 Sep 2016 10:20:03 +0200 [thread overview]
Message-ID: <2417272.QXHhLvSnBg@sagittea> (raw)
In-Reply-To: <87vayau5yt.fsf@dell.be.48ers.dk>
On Monday 05 September 2016 10:05:30 Peter Korsgaard wrote:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-
electrons.com> writes:
> Hi,
>
> >> > However, we could discuss whether it really makes sense to use
> >> > https:// as the main download location when all downloads anyway
> >> > fall
> >> > back to downloading from sources.buildroot.net over http://.
[...]
> - Do nothing. The issue is not so big, and presumably will get smaller
> over time as older distributions get updated.
>
> - Change HTTPS URLs to HTTP where possible. Notice that these days a
> number of websites use HSTS headers to enforce HTTPS. I'm not sure
> when HSTS support got added to wget though (not clear from
> changelog)
>
> - Pass --no-check-certificate in BR2_WGET to disable the check,
> working around the issues.
>
> What do you say?
wget exit with error code '5' if it detect an SSL verification failure.
Buildroot may detect it and display a message explaining how to work
around the problem (something like "Try with BR2_WGET='wget --no-check-
certificate'").
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2016-09-05 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-03 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-09-02 Thomas Petazzoni
2016-09-03 16:03 ` Jérôme Pouiller
2016-09-03 18:10 ` Carlos Santos
2016-09-03 18:36 ` Thomas Petazzoni
2016-09-03 18:59 ` Jérôme Pouiller
2016-09-03 21:23 ` Thomas Petazzoni
2016-09-05 8:05 ` Peter Korsgaard
2016-09-05 8:20 ` Jérôme Pouiller [this message]
2016-09-05 9:30 ` Yann E. MORIN
2016-09-05 16:09 ` Peter Korsgaard
2016-09-05 16:22 ` Jérôme Pouiller
2016-09-05 6:40 ` Peter Korsgaard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2417272.QXHhLvSnBg@sagittea \
--to=jezz@sysmic.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.