diff options
| author | Hugo Landau <hlandau@openssl.org> | 2023-11-28 07:39:41 +0000 |
|---|---|---|
| committer | Hugo Landau <hlandau@openssl.org> | 2023-12-06 10:40:11 +0000 |
| commit | e6cf72c525494d95f58e8c17db2c003eba8ffd87 (patch) | |
| tree | c01b3cba29680a0d8c0e60b73705cb0cbd052912 /include | |
| parent | cd4edeb2f75dd12bb42c1b8886204a7a4029323b (diff) | |
QUIC LCIDM: Always use lcid_obj to refer to QUIC_LCID
Reviewed-by: Neil Horman <nhorman@openssl.org>
Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/22673)
Diffstat (limited to 'include')
| -rw-r--r-- | include/internal/quic_lcidm.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/include/internal/quic_lcidm.h b/include/internal/quic_lcidm.h index 6c040f80be..9b11429814 100644 --- a/include/internal/quic_lcidm.h +++ b/include/internal/quic_lcidm.h @@ -87,7 +87,7 @@ * DCID length, it logically follows that an ODCID can never be used in a 1-RTT * packet. This is fine as by the time the 1-RTT EL is reached the peer should * already have switched away from the ODCID to a CID we generated ourselves, - * and if this is not happened we can consider that a protocol violation. + * and if this has not happened we can consider that a protocol violation. * * In any case, this means that the LCIDM must necessarily support LCIDs of * different lengths, even if it always generates LCIDs of a given length. |