Re: [quicwg/base-drafts] Conflicting error codes (#4087)

[Christian Huitema <[e-mail]>]

I am trying to write a test for the generation of the key update error code. This is a bit hard, since by default the implementation will rotate keys after sending more than <close-to-the-limit> packets, and thus the condition is not seen. One could test that the peer has sent more than <limit> packets without rotating the keys, but then there is some fuzziness to what the limit is. For example, for AES GCM, should that be "received 2**25 packets" or "2**25 + 1"?

The error is also a bit silly. It requires tracking how many packets were decrypted with a given key, and then disconnecting with a specific error if the limit is exceeded. But the node that tracks the limit could also unilaterally trigger a key rotation if the receive count is getting close enough. Of course, the non-standard peer could refuse to update its own key, and never rotate the key phase. Is *that* the condition for KEY_UPDATE_ERROR?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4087#issuecomment-692132583