Question for US Rules committee on AH capability within LX NAV computers?
On Apr 16, 3:21*pm, Don Johnstone wrote:
That is not going to work. The same private code is used in many flight
recorders, so all you have to do is break into one and break into the
software. You then have the private key for all similar flight recorders.
Mine as you put it is still intact. It is pointless relying on a private
key of any length if you are going to put it out into the world in an
easily available box, that is not security, that is total ignorance and I
suspect the penny has already dropped with the IGC as well, took em long
enough.
Don, use of a single private key for multiple units of a given
approved flight recorder model is not permissible. Each flight
recorder unit must have a unique private key. This requirement was
added to the specification in 2001 (AL4), after it was shown that one
design (since updated) had this flaw. See section 6.1 and Appendix G
of the IGC Technical Specification for GNSS Flight Recorders, if it
amuses you.
Any device that is freely available to a community at large (as
opposed to locked away in safes) can't be 100% free of security
issues, but shared private keys is not one of them...
Marc
|