New "spoofing" attacks resulting in total navigation failure have been occurring above the Middle East for months, which is "highly significant" for airline safety.
Commercial Flights Are Experiencing 'Unthinkable' GPS Attacks and Nobody Knows What to Do::New "spoofing" attacks resulting in total navigation failure have been occurring above the Middle East for months, which is "highly significant" for airline safety.
This sounds rather dangerous. GPS was originally opened up to civilian use for the purpose of keeping flights on course, after the disaster of Korean Air Flight 007 straying into Soviet airspace and being shot down back in the 1980s.
I can't understand what is to be gained by deliberately trying to knock civilian airliners off course.
GPS guided drone attacks. Civilian GPS top out at 300 m a second. Anything beyond that is a missile and GPS refuses to work unless you have one of the special government GPS chips without the limiter.
Would that be relevant for a drone attack? I wouldn't think a drone that isn't operated by a state actor is likely to be moving that fast, and presumably a state actor could build their own chips without a limiter?
The GPS chips have internal limits on how fast they think they can move. If they determine that they are moving faster than 300m/s they will stop outputting any results for a period of time. This limit is, IIRC, put in at the silicon level, so only military chips can bypass it.
If you try to use mapping apps on a plane you sometimes run into this issue.
It is trivial to make your GPS receiver firmware ignore these limits. There are even open-source receivers (SwiftNav piksi, for example). Modifying a binary is much harder, but not impossible for a motivated state like Iran or Russia. It's best to think of the COCOM limits as suggestions.
But even the fastest airliners at the moment (A330 neo) moves slower than 300m/s. Wikipedia claims that COCOM limits are even higher so I don't think that they are the reason for the inaccurate tracking on planes.
Oh, neat. I was not aware of that. I have seen that before but thought it was due to the phone not being able to lock on to the signal from inside a big metal tube.