[14144] in cryptography@c2.net mail archive
Re: fyi: bear/enforcer open-source TCPA project
daemon@ATHENA.MIT.EDU (Sean Smith)
Wed Sep 10 14:18:29 2003
X-Original-To: cryptography@metzdowd.com
X-Original-To: cryptography@metzdowd.com
To: cryptography@metzdowd.com
In-Reply-To: Your message of "Wed, 10 Sep 2003 10:49:15 PDT."
<Pine.LNX.4.53L0.0309100952260.11624@bolt.sonic.net>
From: Sean Smith <sws@cs.dartmouth.edu>
Reply-To: Sean Smith <sws@cs.dartmouth.edu>
Date: Wed, 10 Sep 2003 13:57:41 -0400
> So this doesn't
> work unless you put a "speed limit" on CPU's, and that's ridiculous.
Go read about the 4758. CPU speed won't help unless
you can crack 2048-bit RSA, or figure out a way around
the physical security, or find a flaw in the application.
> Yes. Protocol designers have been explaining how to do them for
> decades.
But (at a high-level) there are things that are awkward
or extremely impractical to do with, say, multi-party computation.
That's where the "secure hardware" work---from Abyss, to TCPA, to
plastic-speckles, to the CPU+ work at MIT and Princeton---comes in.
--Sean
--
Sean W. Smith, Ph.D. sws@cs.dartmouth.edu
http://www.cs.dartmouth.edu/~sws/ (has ssl link to pgp key)
Department of Computer Science, Dartmouth College, Hanover NH USA
---------------------------------------------------------------------
The Cryptography Mailing List
Unsubscribe by sending "unsubscribe cryptography" to majordomo@metzdowd.com
