Red V symbol (log file not valid) after OLC upload.

On Nov 24, 3:00*am, Max Kellermann wrote:
If they had a different private key, then VALI.exe would need to
include all public keys of all loggers sold. *And you would have to
update the VALI.exe each time the vendor generates new keys for new
loggers he will sell, and each time somebody wants to have his logger
repaired. *Then think about what happens when a pilot sends a logger
for repair, how will inserting a new key into the logger work? *How
will the existing VALI.exe on the OLC server get to know about this?

While that would be technically possibly, and it would be possible to
pregenerate thousands of keys in advance, I do not think any logger
vendor has done this.

Do you think they did?

The vendors of IGC approved flight recorders are required to do this,
as spelled out in the specification, which can be obtained here
(unfortunately, the FAI web site is a bit wonky, right now):

http://www.fai.org/igc-documents

All flight recorders currently approved for "all flights" or "all
badges and diplomas" have unique public/private key pairs for each
unit. I, as a member of the IGC GNSS Flight Recorder Approval
Committee, would like to see the algorithms standardized and the
public keys openly distributed, but life is always a bit more
complicated than it might seem...

Marc