Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] utils/genrandconfig: use --no-check-certificate in wget by default
Date: Tue, 10 Oct 2017 22:25:43 +0200	[thread overview]
Message-ID: <20171010222543.0beed48d@windsurf.lan> (raw)
In-Reply-To: <20170902212938.23712-1-thomas.petazzoni@free-electrons.com>

Hello,

On Sat,  2 Sep 2017 23:29:38 +0200, Thomas Petazzoni wrote:
> A number of autobuilder failures are due to the fact that autobuilder
> instances use old distributions, with old SSL certificates, and
> therefore wget aborts with an error "The certificate of `xyz.org' is
> not trusted.".
> 
> In order to avoid such failures that are not very interesting in the
> context of the autobuilders, we pass --no-check-certificate to
> wget. The integrity of the downloaded files is anyway verified by the
> hashes, and this is only meant to be used in the context of
> testing/CI, not in production.
> 
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Would it be possible to get some feedback on this patch?

We recently bump dbus to 1.10.24, and look how the autobuilders are
"polluted" by this certificate issue:
http://autobuild.buildroot.net/?reason=dbus-1.10.24.

We've got two options: either we do it in utils/genrandconfig as
proposed, or we do it in the autobuild-run script that runs on the
autobuilder slaves.

Comments ?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-10-10 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-02 21:29 [Buildroot] [PATCH] utils/genrandconfig: use --no-check-certificate in wget by default Thomas Petazzoni
2017-10-10 20:25 ` Thomas Petazzoni [this message]
2017-10-10 21:25   ` Arnout Vandecappelle
2017-10-11  6:53     ` Thomas Petazzoni
2018-03-31 15:19       ` Arnout Vandecappelle

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=20171010222543.0beed48d@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox