From: Valdis.Kletnieks@vt.edu
To: Dave Taht <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
fcc@lists.prplfoundation.org,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] some comments from elsewhere on the lockdown
Date: Wed, 30 Sep 2015 15:56:59 -0400 [thread overview]
Message-ID: <16684.1443643019@turing-police.cc.vt.edu> (raw)
In-Reply-To: <CAA93jw7FrGr+GCuNnOh6ugGrA_81KN07+s6zTenuMX56pG_vzg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1283 bytes --]
On Fri, 25 Sep 2015 22:40:02 +0100, Dave Taht said:
Sorry for late reply...
> 2) Mandate that: the vendor supply a continuous update stream, one
> that must respond to regulatory transgressions and CVEs within 45 days
> of disclosure, for the warranted lifetime of the product + 5 years
> after last customer ship.
This needs to address vendors going out of business, and also corporate
acquisitions.
Bonus points for explaining how to deal with a CVE against hardware that's 7
years and 10 months out of production (3 years warranty + 5) - that requires a
hardware engineering change to properly close.
(I once got my chops busted by somebody from the GNU project over clause
3B of the GPLV2:
b) Accompany it with a written offer, valid for at least three
years, to give any third party, for a charge no more than your
cost of physically performing source distribution, a complete
machine-readable copy of the corresponding source code, to be
distributed under the terms of Sections 1 and 2 above on a medium
customarily used for software interchange; or,
Apparently, they were of the opinion that the mere fact that I might
die of a heart attack a year after distributing something doesn't
excuse me from complying.)
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2015-09-30 19:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 19:49 Dave Taht
2015-09-25 20:16 ` David P. Reed
2015-09-25 21:40 ` Dave Taht
2015-09-26 1:08 ` David P. Reed
2015-09-30 19:56 ` Valdis.Kletnieks [this message]
[not found] ` <c4cfac093cff8fefa8cd763dab8f04a0@thinkpenguin.com>
2015-09-30 20:51 ` [Cerowrt-devel] [FCC] " Valdis.Kletnieks
2015-10-01 10:33 ` David P. Reed
2015-10-01 11:15 ` Dave Taht
2015-10-02 14:22 ` [Cerowrt-devel] Editorial questions for response to the FCC Rich Brown
2015-10-02 20:21 ` dpreed
2015-09-26 9:46 ` [Cerowrt-devel] some comments from elsewhere on the lockdown Laurent GUERBY
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=16684.1443643019@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=fcc@lists.prplfoundation.org \
--cc=make-wifi-fast@lists.bufferbloat.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