Marc wrote:
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.

Food for thought (opening Pandora's box a little):

The VALI-xxx.EXE (or the according DLL) needs to contain all public
keys of all flight recorders of its kind.

Does everybody have to update their VALI-xxx.EXE when I send my flight
recordor for seal repair to the manufacturer?
If not, how else are new public keys distributed?

(Yes, there are other technical solutions like including the signed
certificate and the public key in the G record, but this technology
has not been documented and peer reviewed, and crypto technology that
hasn't been peer reviewed is insecure more often than not.)

Max