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.

  • shortwavesurfer@monero.town
    link
    fedilink
    English
    arrow-up
    3
    arrow-down
    2
    ·
    1 year ago

    Are you meaning 300 measurements per second? Because civilian gps has an accuracy of ~3 meters. I may be misunderstanding though

    • ironeagl@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      1
      ·
      1 year ago

      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.

      • sanmarzano@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        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.

      • EarMaster@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        1 year ago

        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.

      • shortwavesurfer@monero.town
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        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.