In the TacView Real-time Telemetry docs[1], it talks about how the password hash uses CRC-64-ECMA. However, from sniffing the TCP stream, using online CRC-64[2] encoders, and going so far as implementing my own version of CRC-64-ECMA in two different languages[3], it looks like the Tacview client uses it in a different way or I'm interpreting it incorrectly:
As an example, when I encode 'glen':
The TacView client and server use and expect: '2f43af03508ceac5' or '37bcf8f2' (it seems to send both in separate packets)
CRC64ECMA creates: 'aa3a22c699bca958'
It's only when I use the 32-bit hash, "37bcf8f2", that I can create a connection, but I don't know what algorithm created that hash.
I searched the forum and couldn't find anything relevant - does anyone have any hints or guidance here?
[1]
https://www.tacview.net/documentation/realtime/en/[2]
https://crc64.online/[3]
https://github.com/glenmurphy/crc64