[148122] in cryptography@c2.net mail archive
Re: [Cryptography] [cryptography] NIST Randomness Beacon
daemon@ATHENA.MIT.EDU (Peter Gutmann)
Mon Nov 11 18:36:30 2013
X-Original-To: cryptography@metzdowd.com
Date: Tue, 12 Nov 2013 12:28:04 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: andrew@acooke.org, warren@kumari.net
In-Reply-To: <D2DBE8C7-CECA-466F-B2D2-8542D0789722@kumari.net>
Cc: cypherpunks@cpunks.org, cryptography@metzdowd.com,
cryptography@randombit.net
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com
--===============6213789742553277038==
Content-Type: text/plain
Warren Kumari <warren@kumari.net> writes:
>I've often wondered if there is a clever way to do the inverse -- basically
>to have a "latest" timestamp? This seems like a much harder problem -- 'm
>looking for a "movie plot" type solution that the public can easily
>understand…
You could do it with a physical one-way function. Take a photo of the victim
on top of the WTC and you know that it can't have been occurred after 9/11. To
generalise it, photograph the victim in front of some documented object and
then destroy the object. I'm assuming in the movie-plot scenario that someone
who's kidnapped a victim won't worry about blowing up a statue in a park or
performing whatever the physical one-way operation is. Depending on how evil
your movie-plot villain is (and how convoluted the plot will get), he/she
could kill random strangers after photographing them with the victim, in order
to fix a point in time.
Peter.
--===============6213789742553277038==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography
--===============6213789742553277038==--
