>[Line] fixed it by adding a random number to the user's destination This is a imperfect solution. There's two possibilities: the offset (aka "random number") is dynamic, or it's fixed. If it's the former all you have to do is sample enough times to get through the noise. If it's the latter, it's not vulnerable to the previous attack, but if you have a known point of reference (so you can deduce what the offset is),…
> If it's the latter, it's not vulnerable to the previous attack, but if you have a known point of reference (so you can deduce what the offset is) It sounds like this approach could be prevented by having a random fixed offset for each user, so that you have no point of reference unless you already know where that specific user is. [Removed bit about regenerating this offset infrequently.] EDIT: You could even do th…
(i.e. you're unlikely to most of the time be in the middle of a lake, farm field etc)