Here are the classes, structs, unions and interfaces with brief descriptions:
[detail level 12]
▼Ncrypto | The cryptographic implementations for WireGuard |
Ckeypair | A simple private-public keypair |
Cstring | A cryptographically secure string |
▼Nnetwork | The core networking namespace |
Cqueue | A thread-safe queue |
▼Nshared | The shared namespace |
Cconnection | |
Csys_packet | A system packet |
▼Nudp | This namespace includes the UDP implementation, |
Cpacket | A UDP Packet |
▼Nwireguard | This namespace includes the WireGuard implementation, |
Cconfig | A WireGuard Configuration |
CCookiePacket | |
CInitPacket | The initial packet sent from initiator to responder |
CPacket | For both security and ease of use, we want to use crypto::string as much as possible. This makes it easy to run all our cryptographic functions on the handshake and transport, but it raises an issue in that these objects are not contiguous values in memory (Or, they are, but casting it into a character array isn't going to get you the bytes). If you tried to just cast the string and send it across the wire, you'd get garbage. Instead, we need to Serialize and Expand from a collection of crypto::strings making up a packet (Whether that be the handshake packets or transport packets), so that we can work with crypto::string, but be able to serialize it down when we need to send it, and construct it back from bytes when receiving it. To unify this functionality, the Packet object contains a list of crypto::string's in a vector and will serialize the contents of it, and construct a itself from bytes. Other objects derive from this class, and specify the size of the vector and its elements, and values to access specific parts |
CResponsePacket | The packet sent by the responder to the initiator during the handshake |
CRm | A controlled wrapper for the secret random value used for the WireGuard cookies |
CTransportPacket | A WireGuard packet for sending Transport Messages |