News for hackers. Stuff that matters.
Re:Flightradar24 – how it works by loeg on Sunday February 17, 2019 @04:52PM (#19187145)
Do you have more detail on how collection messes with MLAT calculations? It seems like for triangulation purposes, each device should produce some precise timestamp that is not affected by store-and-forward transmission.
Re:Flightradar24 – how it works by sorenjan on Monday February 18, 2019 @12:59AM (#19188898)
I don't think the programs are made to handle that use case. At present you register your receiver's location with the server once and send packets as they arrive, that server doesn't know that your packets are from multiple receivers at multiple locations.

https://discussions.flightaware.com/t/aggregation-of-dump109...

https://github.com/mutability/mlat-client

Re:Flightradar24 – how it works by theyinwhy on Sunday February 17, 2019 @04:59PM (#19187174)
Unfortunately, there is no good solution for this. Either you rely on the time settings of the sender or on the time needed to transmit the data and on the time the data gets transmitted.
Re:Flightradar24 – how it works by wbl on Sunday February 17, 2019 @06:51PM (#19187663)
A radio receiver with a GPS time base doesnt seem that tricky.
Re:Flightradar24 – how it works by lmz on Sunday February 17, 2019 @07:07PM (#19187729)
If we assume the sender is not malicious, a properly configured NTP client ("the time settings of the sender") would probably suffice. If the sender is malicious, unless you somehow make the "signal + timestamp" from the receiver non-modifiable from the receiver to the service, you've lost anyway.
Re:Flightradar24 – how it works by toomuchtodo on Sunday February 17, 2019 @07:33PM (#19187844)
Because MLAT relies on multiple devices, it should be straightforward to identify and blacklist a sender tampering with timing data.