To: | [email protected], [email protected], [email protected] |
---|---|
Subject: | LF: Beacon Timestamp idea |
From: | Talbot Andrew <[email protected]> |
Date: | Thu, 9 Nov 2006 15:51:50 -0000 |
Cc: | "Gannaway, Julian" <[email protected]>, James R Miller <[email protected]> |
Delivered-to: | [email protected] |
Reply-to: | [email protected] |
Sender: | [email protected] |
On my website www.scrbg.org/g4jnt/ I've placed a document (Beacon Timestamp) describing an idea for adding a three letter timestamp transmission to beacons that would allow verification of their reception. The idea is that only the beacon keeper(s) can verify that the received code was actually the one sent at the particular date/time reported. I've already written the code for generating the timestamp into a PIC keyer and its undergoing testing. Still need to add the data format of a few different GPS receivers, then will install on one or more of the Bell Hill beacons at some point in the future. Meanwhile, if there are any cryptologists out there who want to try to show how useless my time hashing algorithm is, and how anyone could falsify reporting, feel free to try to crack it. Andy G4JNT / G8IMR "The Information contained in this E-Mail and any
subsequent correspondence"
"is private and is intended solely for the intended recipient(s)." "For those other than the recipient any disclosure, copying, distribution, " "or any action taken or omitted to be taken in reliance on such information is" "prohibited and may be unlawful." |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | LF: RU6LA's beacon, F4DTL |
---|---|
Next by Date: | Re: LF: RU6LA's beacon, markusvester |
Previous by Thread: | LF: RU6LA's Beacon, lawrence mayhead |
Next by Thread: | LF: HP3586B help please, Conard WS4S |
Indexes: | [Date] [Thread] [Top] [All Lists] |