From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [psa] various server software upgrades
Date: Tue, 8 Dec 2015 12:27:52 -0500 [thread overview]
Message-ID: <20151208172752.GM11489@vapier.lan> (raw)
In-Reply-To: <87poygnb6l.fsf@dell.be.48ers.dk>
On 08 Dec 2015 17:43, Peter Korsgaard wrote:
> >>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
>
> >> I don't believe we will ever bootstrap wget, but we might add
> >> --no-check-certificates in the future (with the download hashes,
> >> checking certificates doesn't add much).
>
> > except there is no checking on the initial download.
>
> With initial download I take it you mean Buildroot, right? That we have
> alternatives for (gpg signatures, git clones, download though browser) -
> But sources.buildroot.{net,org} is almost exclusively used by wget, so I
> prefer to not break it for non-sni capable versions.
realistically, how many people do you think actually leverage gpg
signatures ? having transparent https is better imo than people
running old insecure setups and just telling them to use the one
flag when downloading the initial file. if they're running wget,
then they're probably reading some doc right ? just put a foot
note in there mentioning the flag and old clients.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151208/8af0243f/attachment.asc>
next prev parent reply other threads:[~2015-12-08 17:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 7:35 [Buildroot] [psa] various server software upgrades Mike Frysinger
2015-12-02 7:58 ` Lionel Orry
2015-12-02 8:43 ` Peter Korsgaard
2015-12-02 9:25 ` Nikolay Dimitrov
2015-12-02 9:28 ` Nikolay Dimitrov
2015-12-02 17:31 ` Mike Frysinger
2015-12-02 18:38 ` Nikolay Dimitrov
2015-12-06 21:42 ` Yann E. MORIN
2015-12-06 22:00 ` Peter Korsgaard
2015-12-07 1:55 ` Mike Frysinger
2015-12-07 6:34 ` Peter Korsgaard
2015-12-07 18:51 ` Mike Frysinger
2015-12-07 20:37 ` Peter Korsgaard
2015-12-07 21:55 ` Mike Frysinger
2015-12-07 22:16 ` Peter Korsgaard
2015-12-07 22:54 ` Mike Frysinger
2015-12-07 23:02 ` Yann E. MORIN
2015-12-07 23:22 ` Mike Frysinger
2015-12-08 7:52 ` Peter Korsgaard
2015-12-08 16:40 ` Mike Frysinger
2015-12-08 16:43 ` Peter Korsgaard
2015-12-08 17:27 ` Mike Frysinger [this message]
2015-12-08 7:50 ` Peter Korsgaard
2015-12-08 0:17 ` Mike Frysinger
2015-12-08 7:55 ` Peter Korsgaard
2015-12-08 16:38 ` Mike Frysinger
2015-12-07 8:00 ` Peter Korsgaard
2015-12-07 8:23 ` Peter Korsgaard
2015-12-07 18:52 ` Mike Frysinger
2015-12-07 19:57 ` Mike Frysinger
2015-12-07 19:59 ` Yann E. MORIN
2015-12-07 23:52 ` Mike Frysinger
2015-12-07 20:42 ` 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=20151208172752.GM11489@vapier.lan \
--to=vapier@gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox