I am thinking of how to prevent GPS spoofing in HTML5 by simulator mock location.
These are some of my ideas:
-
take more than one sample. In real situation, the GPS location should be moving. There should be some differences in real situation.
-
use a key to encrypt the data, so that the spoofers cannot see what is sending to server. But, by looking at the alogthrm in the code, they may be able to look at what are sending to the servers.
I know it is not easy in real situation. But still, I would like to prevent some of the cases. Do you have any other suggestions?
This is based on a fundamental misunderstanding of the spec. It explicitly states:
In other words, you’re futilely trying to prevent something the specification explicitly allows.
Technically, it is also not that hard to create arbitrary user input. Some highways are very straight, so a straight path with a small random perpendicular error is plausibly someone riding in a car.