Uses of Record Class
io.github.mahmoudimus.quic.crypto.Keys
Packages that use Keys
Package
Description
The sans-I/O QUIC connection and endpoint, ported from quinn-proto: the
Connection state machine (handshake, packet assembly and
processing, key updates, closing and draining), the Endpoint that routes datagrams and answers with Version
Negotiation, Retry and stateless resets, their configurations (TransportConfig, ServerConfig, ClientConfig, EndpointConfig), and the building blocks they are made of:
range sets (RangeSet), reassembly of received data
(Assembler), buffering of sent data (SendBuffer), streams and flow control (StreamsState), packet number spaces and ACK generation
(PacketSpace), loss detection (Recovery), pacing (Pacer), path MTU discovery (MtuDiscovery) and timers (TimerTable).QUIC packet protection (RFC 9001 section 5): AEAD payload keys, header protection keys, Initial
keys per version, key updates and the Retry integrity tag.
-
Uses of Keys in io.github.mahmoudimus.quic.connection
Methods in io.github.mahmoudimus.quic.connection that return KeysMethods in io.github.mahmoudimus.quic.connection with parameters of type Keys -
Uses of Keys in io.github.mahmoudimus.quic.crypto
Methods in io.github.mahmoudimus.quic.crypto that return KeysModifier and TypeMethodDescriptionstatic KeysKeys.fromSecrets(Secrets secrets, boolean isServer) QUIC version 1 keys from the traffic secrets the TLS handshake produced.static KeysKeys.fromSecrets(Secrets secrets, boolean isServer, QuicVersion version) Keys from the traffic secrets the TLS handshake produced.static KeysKeys.initial(QuicVersion version, ConnectionId clientDestinationId, boolean isServer) The Initial keys for a client's first Destination Connection ID.Keys.update(Secrets nextSecrets, boolean isServer, QuicVersion version) The keys of the next key phase: new packet keys from the next secrets, with these header keys, which a key update does not change (RFC 9001 section 6).