From: Jason Cooper <jason@lakedaemon.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: ksummit-discuss@lists.linuxfoundation.org,
John Stultz <john.stultz@linaro.org>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Dealing with 2038
Date: Thu, 15 May 2014 22:50:01 -0400 [thread overview]
Message-ID: <20140516025001.GU27822@titan.lakedaemon.net> (raw)
In-Reply-To: <5374F758.7020204@zytor.com>
On Thu, May 15, 2014 at 10:20:24AM -0700, H. Peter Anvin wrote:
> On 05/15/2014 05:18 AM, Grant Likely wrote:
> >
> > And yet still, once deployed will never get updated. :-(
> >
>
> That is a whole separate problem. I'm not quite convinced that it will
> work that way... maybe ubiquitous upgrades will be a solved problem by then.
With the infrastructure to support verification, which brings in key
management. Otherwise, it'll be an easy attack surface. I'm not
optimistic...
The alternative is to make the devices so trivially disposable that
outdated/vulnerable devices are rejected from the network. The user
then orders a replacement.
thx,
Jason.
next prev parent reply other threads:[~2014-05-16 2:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 18:33 John Stultz
2014-05-05 19:23 ` Andy Lutomirski
2014-05-05 20:53 ` josh
2014-05-05 23:20 ` Andy Lutomirski
2014-05-06 2:12 ` H. Peter Anvin
2014-05-06 2:21 ` Josh Triplett
2014-05-06 12:57 ` Theodore Ts'o
2014-05-06 17:53 ` John Stultz
2014-05-06 18:20 ` Arnd Bergmann
2014-05-06 20:19 ` Theodore Ts'o
2014-05-06 20:33 ` josh
2014-05-06 20:50 ` Theodore Ts'o
2014-05-06 22:06 ` John Stultz
2014-05-07 2:07 ` Theodore Ts'o
2014-05-07 11:19 ` Jonathan Corbet
2014-05-07 17:28 ` John Stultz
2014-05-09 15:05 ` Theodore Ts'o
2014-05-08 20:37 ` Ben Hutchings
2014-05-09 15:10 ` Theodore Ts'o
2014-05-09 20:39 ` Arnd Bergmann
2014-05-09 22:33 ` Josh Triplett
2014-05-10 0:16 ` H. Peter Anvin
2014-05-10 1:44 ` Rafael J. Wysocki
2014-05-15 12:18 ` Grant Likely
2014-05-15 17:20 ` H. Peter Anvin
2014-05-16 2:50 ` Jason Cooper [this message]
2014-05-10 0:19 ` Andy Lutomirski
2014-05-06 21:17 ` Daniel Phillips
2014-05-06 21:56 ` Luck, Tony
2014-05-07 1:56 ` Daniel Phillips
2014-05-07 14:00 ` Grant Likely
2014-05-09 17:30 ` H. Peter Anvin
2014-05-06 1:25 ` Li Zefan
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=20140516025001.GU27822@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=ksummit-discuss@lists.linuxfoundation.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