[quicwg/base-drafts] CONNECTION_CLOSE for unpadded Initial (#3269)

[Martin Thomson <[e-mail]>]

The draft requires that if an Initial packet is not padded, the server sends a CONNECTION_CLOSE.  I think that the goal was to have the server drop those packets and *optionally* send a signal.  But that only applies if the server hasn't established state.  We should reword that.


@nibanks says:
> I'm more worried about this as an attack vector. Now that we support multiple initial packets for the client initial, there is more of a windows for an attacker to race a bad initial packet. Sending a 1 byte initial packet to kill your connection would be pretty easy; especially since the size validation check is going to happen pre-decryption, so the attacker doesn't even need to craft a well-formed packet.

_Originally posted by @nibanks in https://github.com/quicwg/base-drafts/pull/3262_

-- 
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/3269