OLC and Cambridge 10/20/25 support ending

On Dec 11, 11:11*pm, Max Kellermann wrote:
You're right by saying it's an illusion, but I strongly disagree that
a server-side service is a viable solution.

What if you don't have internet access?

What if the server is down?

What if the server is commercial (like the OLC), and I object to use
that?

Please note that this thread is entitled "OLC and Cambridge 10/20/25
support ending", and that it is quite hard to use the OLC without at
least occasional access to the internet, and some amount of
willingness to put up with OLC policies.

This problem is not something that should put Cambridge owners in a
dependency situation on one entity. *This problem can be solved with a
free tool that does not require internet connection, and that does not
require this kind of dependency. *If such a solution is possible, it
should be done that way.

The owners of every approved flight recorder, so far, are each
dependent on the manufacturer of their flight recorder, nothing is
different here. Validation source code has never been publicly
released for any approved flight recorder, although that might well
change some day. In any case, usable validation source code for the
GPS-NAV can never be released, as it does not use public key
cryptography.

If this can technically only be achieved by storing the whole verbatim
Cambridge file (including the verbatim signature; using base64?) in
the IGC file, then be it so. *It's not 1995 anymore, and inflating the
IGC files is the lesser evil.

That can be done, and then what? At the other end, you'd need to
extract the embedded CAI file, and run VALI-CAM.exe followed by CONV-
CAM.exe to be certain of getting the valid IGC file. It would be
simpler to submit the original CAI file in the first place...

Marc