Question: Does the webserver need to save the IVs? about netcode HOT 3 CLOSED

Encryption of the challenge token data is performed with the libsodium AEAD primitive crypto_aead_chacha20poly1305_ietf_encrypt with no associated data, a random key generated when the dedicated server starts, and a sequence number that starts at zero and increases with each challenge token generated. The sequence number is extended by padding high bits with zero to create a 96 bit nonce.

If the server restarts, do we generate a new key and start from 0? Keeping the old key and restarting from 0 is a bad idea.

from netcode.

The private portion is encrypted and signed with a private key shared between the web backend and dedicated server instances.

This sharing means we reuse the private key. How do we make sure that iv incrementing is synchronized.

from netcode.

This sharing means we reuse the private key. How do we make sure that iv incrementing is synchronized.

The private key is shared but the nonce is a sequence number that increments with each connect token generated by the matcher. If the matcher shuts down, it should for best practice, not restart the nonce at zero, but continue with the last sequence # generated + 1.

cheers

from netcode.