Help us with this petition for security on anti-collision systems

On Thu, 28 May 2015 13:58:39 +0000, Tim Newport-Peace wrote:

Firstly, the Easter Egg was built into the previous version of FLARM
firmware long before OGN can into being. OGN was not the cause. As I
understand it the Easter Egg was to ensure that users were on reasonably
up-to-date Firmware.

By Easter Egg, do you mean the protocol expiry date? If so its not what I
was talking about and I don't have a problem with it: given that FLARM
was designed for small, low-powered hardware, syncing protocol version
that way makes a helluva lot more sense that having to maintain backward
compatibility over the last 'n' protocol versions just because some lazy
git can't be bothered to keep his software up to date.

Secondly, any transmissions received by an OGN Receiver that have the
Do-Not-Track bit set are discarded at the receiver. There are never sent
to the Server.

Not necessarily: you can't guarantee anything like that if the receiver
is the result of a third party reverse engineering project, which is what
I've always heard about the RPi-hosted FLARM receiver units. If the
software author decides he wants to see everybody and ignores that bit
then pop goes your invisibility cloak.


--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |