Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Jim Gettys <jg@freedesktop.org>
Cc: "David P. Reed" <dpreed@deepplum.com>,
	cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Bloat] plenty of huawei in the news today
Date: Thu, 28 Mar 2019 16:12:56 -0400	[thread overview]
Message-ID: <24490.1553803976@turing-police> (raw)
In-Reply-To: <CAGhGL2AtrVLP9OZ-Cz-vYz5pwXx4yLRwfsAHbXyjm90jievDJw@mail.gmail.com>

On Thu, 28 Mar 2019 14:44:28 -0400, Jim Gettys said:

> My solution is more radical: all the vendors should be held to much higher
> standards, including reproducible builds (something that the UK government
> has been trying to get them to do for years, and failed).

All too often, even getting the *claimed* configuration that was built is far
too difficult. For example, if I ssh to my Lede router, getting it to cough up the
contents of the .config used to build it is a challenge - /proc/config.gz doesn't
hold the userspace part of the config.

  parent reply	other threads:[~2019-03-28 20:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 17:55 [Cerowrt-devel] " Dave Taht
2019-03-28 18:16 ` David P. Reed
2019-03-28 18:16   ` Dave Taht
2019-03-28 18:32     ` David P. Reed
2019-03-28 18:38       ` Dave Taht
2019-03-28 18:44       ` [Cerowrt-devel] [Bloat] " Jim Gettys
2019-03-28 18:47         ` Dave Taht
2019-03-28 20:12         ` Valdis Klētnieks [this message]
2019-03-28 22:23         ` David P. Reed

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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=24490.1553803976@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@deepplum.com \
    --cc=jg@freedesktop.org \
    /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