From: “E. ALLEN SMITH” <EALLENSMITH@ocelot.Rutgers.EDU>
To: hfinney@shell.portal.com
Message Hash: 9c8cb11e31ebdb177b1a27ab9e3bc3c7e51d5d65f1efcafaadb650cc4c2d111a
Message ID: <01I3IFBN6U2G8Y51D0@mbcl.rutgers.edu>
Reply To: N/A
UTC Datetime: 1996-04-14 06:34:51 UTC
Raw Date: Sun, 14 Apr 1996 14:34:51 +0800
From: "E. ALLEN SMITH" <EALLENSMITH@ocelot.Rutgers.EDU>
Date: Sun, 14 Apr 1996 14:34:51 +0800
To: hfinney@shell.portal.com
Subject: Re: No matter where you go, there they are.
Message-ID: <01I3IFBN6U2G8Y51D0@mbcl.rutgers.edu>
MIME-Version: 1.0
Content-Type: text/plain
From: IN%"hfinney@shell.portal.com" "Hal" 11-APR-1996 18:06:18.51
>The method of using authenticated devices which provide timestamped
>data from satellites not visible to the authenticating site does not
>need to provide that data in real time. Even if it is delayed so it
>comes in later than the data from the remote site, the verifying site
>can still use it to calculate what the remote site should have been
>seeing, and so get the benefit of using timings from all the satellites
>visible to the remote site (again, assuming the remote site itself has
>a low latency connection to the authenticating site).
In regards to these timestamping devices... how do they know the
correct time? It looks like that would be distortable, and with that, you could
simply simulate the satellites to them via placing the device inside a metal
box and piping in the appropriately modified signals. If it's getting its time
information from the signals themselves, things get even easier.
-Allen
Return to April 1996
Return to ““E. ALLEN SMITH” <EALLENSMITH@ocelot.Rutgers.EDU>”
1996-04-14 (Sun, 14 Apr 1996 14:34:51 +0800) - Re: No matter where you go, there they are. - “E. ALLEN SMITH” <EALLENSMITH@ocelot.Rutgers.EDU>