Daniel McCarney 5138cd81e1 suites: split integrity and confidentiality limit handling ... Previously the `CipherSuiteCommon` type had a `confidentiality_limit` and a `integrity_limit`. Recent refactoring for better downstream QUIC ergonomics has pulled these limits into the `quic::PacketKey` trait. To reduce duplication this commit adjusts our handling of these two limits. For the `integrity_limit`, it was already documented in `CipherSuiteCommon` as being specific to QUIC and irrelevant for TLS over TCP. For this reason we delete the field from `CipherSuiteCommon`, leaving it only in `quic::PacketKey` where it is actually useful. For the `confidentiality_limit` it was described imprecisely and erred on the side of caution, proposing a limit calculated based on QUIC overhead even for the TCP usecase. Now that we've split this field the `CipherSuiteCommon` version's documentation is updated to use a tighter bound for the TCP use-case, and the associated `PacketKey` field can be documented to use the QUIC bound.		2024-02-27 20:08:42 +00:00
..
examples	server: allow acceptor to send alerts after error	2024-02-27 17:10:20 +00:00
src	suites: split integrity and confidentiality limit handling	2024-02-27 20:08:42 +00:00
tests	hpke: reorder seal/open args, less terse arg names	2024-01-09 15:29:07 +00:00
Cargo.toml	add std feature	2024-02-27 14:31:05 +00:00