Meta tags:
description=WireGuard: fast, modern, secure VPN tunnel;
author=Jason A. Donenfeld;

Headings (most frequently used words):

simple, contact, conceptual, overview, about, the, project, network, interface, cryptokey, routing, built, in, roaming, ready, for, containers, learning, more, source, code, license, easy, to, use, cryptographically, sound, minimal, attack, surface, high, performance, well, defined, thoroughly, considered, irc, discussions, mailing, list, email, security,

Text of the page (most frequently used words):
the (111), and (57), wireguard (36), interface (30), peer (30), for (29), send (17), that (17), #network (17), this (16), packet (16), server (13), with (13), are (12), you (12), using (12), public (12), packets (11), endpoint (11), from (10), any (10), list (10), which (10), configuration (10), allowed (10), security (9), key (9), then (9), like (8), more (8), keys (8), when (8), 192 (8), source (7), encrypted (7), client (7), its (7), single (7), simple (7), each (7), project (6), all (6), other (6), there (6), most (6), protocol (6), cryptography (6), can (6), has (6), secure (6), tunnel (6), data (6), will (6), routing (6), issues (5), not (5), into (5), about (5), access (5), internet (5), peers (5), what (5), ips (5), example (5), might (5), udp (5), vpn (5), kernel (4), under (4), email (4), addresses (4), development (4), code (4), whitepaper (4), your (4), able (4), have (4), authenticated (4), both (4), recent (4), they (4), decrypted (4), roaming (4), cryptokey (4), encrypt (4), destination (4), publickey (4), allowedips (4), 168 (4), use (4), ssh (4), state (4), let (4), platform (4), linux (3), only (3), contact (3), much (3), irc (3), where (3), how (3), used (3), technical (3), namespace (3), container (3), sends (3), received (3), clients (3), because (3), just (3), address (3), ipsec (3), simply (3), inside (3), 230 (3), art (3), lmnopqrs (3), okay (3), abcdefgh (3), meant (3), configured (3), openvpn (3), exchanging (3), cross (3), conceptual (3), overview (3), extremely (3), high (3), very (3), research (2), zx2c4 (2), jason (2), donenfeld (2), released (2), itself (2), bsd (2), license (2), please (2), related (2), different (2), com (2), may (2), mind (2), better (2), channel (2), get (2), similar (2), git (2), mailing (2), also (2), repository (2), provides (2), detail (2), quick (2), start (2), learning (2), means (2), through (2), receives (2), ready (2), containers (2), initial (2), endpoints (2), correctly (2), new (2), built (2), such (2), between (2), need (2), but (2), control (2), combination (2), fully (2), capable (2), one (2), table (2), sending (2), behaves (2), sort (2), wants (2), since (2), wildcard (2), asked (2), higo9xnz (2), onto (2), otherwise (2), dropped (2), gn65bkik (2), privatekey (2), listenport (2), 51820 (2), computer (2), simpler (2), 122 (2), called (2), works (2), private (2), out (2), drop (2), 139 (2), 183 (2), 7361 (2), port (2), host (2), over (2), 216 (2), 211 (2), 110 (2), 53133 (2), remote (2), look (2), networking (2), route (2), configure (2), mosh (2), interested (2), reading (2), read (2), general (2), installation (2), thoroughly (2), considered (2), academic (2), speed (2), embedded (2), performance (2), been (2), designed (2), easily (2), even (2), aims (2), easy (2), manage (2), yet (2), fast (2), modern (2), than (2), firm, devoted, information, expertise, edge, copyright, 2015, 2022, rights, reserved, logo, registered, trademarks, components, gplv2, projects, licensed, mit, apache, gpl, depending, context, report, non, alias, privately, particular, reason, reach, keep, though, support, requests, suited, our, team, involved, discussion, activities, occur, submit, patches, style, lkml, joining, having, trouble, setting, best, place, help, discuss, tasks, plan, future, libera, chat, discussions, divided, hosted, elsewhere, consult, several, repositories, consider, glancing, good, idea, practice, addition, description, exchange, commands, create, main, move, belonging, docker, ensures, possible, way, was, originally, created, contains, knows, before, doesn, discovers, examining, originates, changes, own, discover, update, same, authentically, thus, full, ends, sent, tight, coupling, identity, system, administrators, complicated, firewall, extensions, case, rather, match, assured, authentic, greatly, simplifies, management, great, deal, assurance, iptables, rules, actually, doing, intended, them, ipv4, ipv6, fields, encapsulating, necessary, call, association, words, receiving, decrypts, authenticates, looks, compares, see, matching, his, corresponding, after, being, gi6edusyvn8ugxot8qqd6yc, jyizxihp3ginswrfwge, 21841, higo9xnzjmwlkasshitqiybxz0u3wgliuej1pkf8ykw, yanz5tf, lxxjte14tji3zlmnq, hd2ryuigjbgb3fbmk, xtiba5rbouvnh4htodjb6e697qjlert1nab4mzqp8dg, 124, trmvsop4jyqly6rizbgbssqqy3vxi2pi, y71lowwxx0, gn65bkiky1ece9pp1wdc8routkhlf2pfaqydyybz6ea, heart, concept, associating, short, authenticate, passed, around, files, band, method, their, friend, shell, behind, scenes, happening, provide, proper, privacy, authenticity, perfect, forward, secrecy, accept, once, plain, text, properly, remember, got, decrypt, happens, bytes, step, entire, associates, does, following, adding, multiple, etc, normally, routes, added, removed, ordinary, utilities, specific, aspects, tool, acts, ifconfig, wg3, wg2, wg1, wg0, wlan0, eth0, securely, encapsulates, add, across, distribution, pushed, configurations, these, left, layers, lest, end, bloat, ike, contrast, mimics, model, parties, begin, scope, internal, inner, workings, brief, summary, depth, goes, fundamentals, intend, implement, notes, onward, here, progress, quickstart, instructions, result, lengthy, process, resulting, paper, clearly, defines, intense, considerations, went, decision, well, defined, cryptographic, primitives, fact, lives, suitable, small, devices, smartphones, loaded, backbone, routers, ease, implementation, simplicity, implemented, few, lines, auditable, vulnerabilities, compared, behemoths, swan, openssl, auditing, gigantic, codebases, overwhelming, task, large, teams, experts, comprehensively, reviewable, individuals, minimal, attack, surface, uses, trusted, constructions, makes, conservative, reasonable, choices, reviewed, cryptographers, hkdf, siphash24, blake2, poly1305, chacha20, curve25519, noise, framework, cryptographically, sound, deploy, connection, made, exactly, rest, transparently, handled, connections, concerned, daemons, worry, hood, presents, basic, powerful, utilizes, leaner, useful, while, avoiding, massive, headache, intends, considerably, performant, purpose, running, interfaces, super, computers, alike, fit, many, circumstances, initially, now, windows, macos, ios, android, widely, deployable, currently, heavy, already, regarded, easiest, simplest, solution, industry, faster, donate, presentations, todo, known, limitations, build, status, embedding, applications, namespaces, formal, verification, compilation, interworkings, toggle, navigation,

Text of the page (random words):
wireguard fast modern secure vpn tunnel toggle navigation wireguard installation quick start interworkings compilation from source code protocol cryptography formal verification cross platform interface routing network namespaces embedding into applications build status known limitations performance project todo presentations whitepaper donate conceptual overview simple network interface cryptokey routing built in roaming ready for containers learning more about the project source code license wireguard is an extremely simple yet fast and modern vpn that utilizes state of the art cryptography it aims to be faster simpler leaner and more useful than ipsec while avoiding the massive headache it intends to be considerably more performant than openvpn wireguard is designed as a general purpose vpn for running on embedded interfaces and super computers alike fit for many different circumstances initially released for the linux kernel it is now cross platform windows macos bsd ios android and widely deployable it is currently under heavy development but already it might be regarded as the most secure easiest to use and simplest vpn solution in the industry simple easy to use wireguard aims to be as easy to configure and deploy as ssh a vpn connection is made simply by exchanging very simple public keys exactly like exchanging ssh keys and all the rest is transparently handled by wireguard it is even capable of roaming between ip addresses just like mosh there is no need to manage connections be concerned about state manage daemons or worry about what s under the hood wireguard presents an extremely basic yet powerful interface cryptographically sound wireguard uses state of the art cryptography like the noise protocol framework curve25519 chacha20 poly1305 blake2 siphash24 hkdf and secure trusted constructions it makes conservative and reasonable choices and has been reviewed by cryptographers minimal attack surface wireguard has been designed with ease of implementation and simplicity in mind it is meant to be easily implemented in very few lines of code and easily auditable for security vulnerabilities compared to behemoths like swan ipsec or openvpn openssl in which auditing the gigantic codebases is an overwhelming task even for large teams of security experts wireguard is meant to be comprehensively reviewable by single individuals high performance a combination of extremely high speed cryptographic primitives and the fact that wireguard lives inside the linux kernel means that secure networking can be very high speed it is suitable for both small embedded devices like smartphones and fully loaded backbone routers well defined thoroughly considered wireguard is the result of a lengthy and thoroughly considered academic process resulting in the technical whitepaper an academic research paper which clearly defines the protocol and the intense considerations that went into each decision conceptual overview if you d like a general conceptual overview of what wireguard is about read onward here you then may progress to installation and reading the quickstart instructions on how to use it if you re interested in the internal inner workings you might be interested in the brief summary of the protocol or go more in depth by reading the technical whitepaper which goes into more detail on the protocol cryptography and fundamentals if you intend to implement wireguard for a new platform please read the cross platform notes wireguard securely encapsulates ip packets over udp you add a wireguard interface configure it with your private key and your peers public keys and then you send packets across it all issues of key distribution and pushed configurations are out of scope of wireguard these are issues much better left for other layers lest we end up with the bloat of ike or openvpn in contrast it more mimics the model of ssh and mosh both parties have each other s public keys and then they re simply able to begin exchanging packets through the interface simple network interface wireguard works by adding a network interface or multiple like eth0 or wlan0 called wg0 or wg1 wg2 wg3 etc this network interface can then be configured normally using ifconfig 8 or ip address 8 with routes for it added and removed using route 8 or ip route 8 and so on with all the ordinary networking utilities the specific wireguard aspects of the interface are configured using the wg 8 tool this interface acts as a tunnel interface wireguard associates tunnel ip addresses with public keys and remote endpoints when the interface sends a packet to a peer it does the following this packet is meant for 192 168 30 8 which peer is that let me look okay it s for peer abcdefgh or if it s not for any configured peer drop the packet encrypt entire ip packet using peer abcdefgh s public key what is the remote endpoint of peer abcdefgh let me look okay the endpoint is udp port 53133 on host 216 58 211 110 send encrypted bytes from step 2 over the internet to 216 58 211 110 53133 using udp when the interface receives a packet this happens i just got a packet from udp port 7361 on host 98 139 183 24 let s decrypt it it decrypted and authenticated properly for peer lmnopqrs okay let s remember that peer lmnopqrs s most recent internet endpoint is 98 139 183 24 7361 using udp once decrypted the plain text packet is from 192 168 43 89 is peer lmnopqrs allowed to be sending us packets as 192 168 43 89 if so accept the packet on the interface if not drop it behind the scenes there is much happening to provide proper privacy authenticity and perfect forward secrecy using state of the art cryptography cryptokey routing at the heart of wireguard is a concept called cryptokey routing which works by associating public keys with a list of tunnel ip addresses that are allowed inside the tunnel each network interface has a private key and a list of peers each peer has a public key public keys are short and simple and are used by peers to authenticate each other they can be passed around for use in configuration files by any out of band method similar to how one might send their ssh public key to a friend for access to a shell server for example a server computer might have this configuration interface privatekey yanz5tf lxxjte14tji3zlmnq hd2ryuigjbgb3fbmk listenport 51820 peer publickey xtiba5rbouvnh4htodjb6e697qjlert1nab4mzqp8dg allowedips 10 192 122 3 32 10 192 124 1 24 peer publickey trmvsop4jyqly6rizbgbssqqy3vxi2pi y71lowwxx0 allowedips 10 192 122 4 32 192 168 0 0 16 peer publickey gn65bkiky1ece9pp1wdc8routkhlf2pfaqydyybz6ea allowedips 10 10 10 230 32 and a client computer might have this simpler configuration interface privatekey gi6edusyvn8ugxot8qqd6yc jyizxihp3ginswrfwge listenport 21841 peer publickey higo9xnzjmwlkasshitqiybxz0u3wgliuej1pkf8ykw endpoint 192 95 5 69 51820 allowedips 0 0 0 0 0 in the server configuration each peer a client will be able to send packets to the network interface with a source ip matching his corresponding list of allowed ips for example when a packet is received by the server from peer gn65bkik after being decrypted and authenticated if its source ip is 10 10 10 230 then it s allowed onto the interface otherwise it s dropped in the server configuration when the network interface wants to send a packet to a peer a client it looks at that packet s destination ip and compares it to each peer s list of allowed ips to see which peer to send it to for example if the network interface is asked to send a packet with a destination ip of 10 10 10 230 it will encrypt it using the public key of peer gn65bkik and then send it to that peer s most recent internet endpoint in the client configuration its single peer the server will be able to send packets to the network interface with any source ip since 0 0 0 0 0 is a wildcard for example when a packet is received from peer higo9xnz if it decrypts and authenticates correctly with any source ip then it s allowed onto the interface otherwise it s dropped in the client configuration when the network interface wants to send a packet to its single peer the server it will encrypt packets for the single peer with any destination ip address since 0 0 0 0 0 is a wildcard for example if the network interface is asked to send a packet with any destination ip it will encrypt it using the public key of the single peer higo9xnz and then send it to the single peer s most recent internet endpoint in other words when sending packets the list of allowed ips behaves as a sort of routing table and when receiving packets the list of allowed ips behaves as a sort of access control list this is what we call a cryptokey routing table the simple association of public keys and allowed ips any combination of ipv4 and ipv6 can be used for any of the fields wireguard is fully capable of encapsulating one inside the other if necessary because all packets sent on the wireguard interface are encrypted and authenticated and because there is such a tight coupling between the identity of a peer and the allowed ip address of a peer system administrators do not need complicated firewall extensions such as in the case of ipsec but rather they can simply match on is it from this ip on this interface and be assured that it is a secure and authentic packet this greatly simplifies network management and access control and provides a great deal more assurance that your iptables rules are actually doing what you intended for them to do built in roaming the client configuration contains an initial endpoint of its single peer the server so that it knows where to send encrypted data before it has received encrypted data the server configuration doesn t have any initial endpoints of its peers the clients this is because the server discovers the endpoint of its peers by examining from where correctly authenticated data originates if the server itself changes its own endpoint and sends data to the clients the clients will discover the new server endpoint and update the configuration just the same both client and server send encrypted data to the most recent ip endpoint for which they authentically decrypted data thus there is full ip roaming on both ends ready for containers wireguard sends and receives encrypted packets using the network namespace in which the wireguard interface was originally created this means that you can create the wireguard interface in your main network namespace which has access to the internet and then move it into a network namespace belonging to a docker container as that container s only interface this ensures that the only possible way that container is able to access the network is through a secure encrypted wireguard tunnel learning more consider glancing at the commands quick start for a good idea of how wireguard is used in practice there is also a description of the protocol cryptography key exchange in addition to the technical whitepaper which provides the most detail about the project source code wireguard is divided into several repositories hosted in the zx2c4 git repository and elsewhere consult the project repository list irc discussions if you re having trouble setting up wireguard or using it the best place to get help is the wireguard irc channel on libera chat we also discuss development tasks there and plan the future of the project mailing list get involved in the wireguard development discussion by joining the mailing list this is where all development activities occur submit patches using git send email similar to the style of lkml email contact if you d like to contact us privately for a particular reason you may reach us at team wireguard com keep in mind though that support requests are much better suited for our irc channel security contact please report any security issues to and only to security wireguard com do not send non security related issues to this email alias do not send security related issues to different email addresses license the kernel components are released under the gplv2 as is the linux kernel itself other projects are licensed under mit bsd apache 2 0 or gpl depending on context copyright 2015 2022 jason a donenfeld all rights reserved wireguard and the wireguard logo are registered trademarks of jason a donenfeld this project is from zx2c4 and from edge security a firm devoted to information security research expertise