I'm speaking out of ignorance here, but why couldn't you just use a quantitized time value (to account for transmission lag) as a part of the data that's hashed? It works great to prevent replay attacks with OAuth.
nope. it's time that is the factor for triangulation. you always take the first time you received from the one source and you can discard certainly something way out side of what you expect. It's how you defeat the concreate canyon effect in big cities where signals are bouncing off everything.
However if you have a low strength signal from one source and you receive a frame that is a second or a two off, it can cause you to think you are miles away from where you think you supposed to be.
Comments
I'm speaking out of ignorance here, but why couldn't you just use a quantitized time value (to account for transmission lag) as a part of the data that's hashed? It works great to prevent replay attacks with OAuth.
nope. it's time that is the factor for triangulation. you always take the first time you received from the one source and you can discard certainly something way out side of what you expect. It's how you defeat the concreate canyon effect in big cities where signals are bouncing off everything.
However if you have a low strength signal from one source and you receive a frame that is a second or a two off, it can cause you to think you are miles away from where you think you supposed to be.