| 1 | .\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05) |
1 | .\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.30) |
| 2 | .\" |
2 | .\" |
| 3 | .\" Standard preamble: |
3 | .\" Standard preamble: |
| 4 | .\" ======================================================================== |
4 | .\" ======================================================================== |
| 5 | .de Sh \" Subsection heading |
|
|
| 6 | .br |
|
|
| 7 | .if t .Sp |
|
|
| 8 | .ne 5 |
|
|
| 9 | .PP |
|
|
| 10 | \fB\\$1\fR |
|
|
| 11 | .PP |
|
|
| 12 | .. |
|
|
| 13 | .de Sp \" Vertical space (when we can't use .PP) |
5 | .de Sp \" Vertical space (when we can't use .PP) |
| 14 | .if t .sp .5v |
6 | .if t .sp .5v |
| 15 | .if n .sp |
7 | .if n .sp |
| 16 | .. |
8 | .. |
| 17 | .de Vb \" Begin verbatim text |
9 | .de Vb \" Begin verbatim text |
| … | |
… | |
| 44 | .el\{\ |
36 | .el\{\ |
| 45 | . ds -- \|\(em\| |
37 | . ds -- \|\(em\| |
| 46 | . ds PI \(*p |
38 | . ds PI \(*p |
| 47 | . ds L" `` |
39 | . ds L" `` |
| 48 | . ds R" '' |
40 | . ds R" '' |
|
|
41 | . ds C` |
|
|
42 | . ds C' |
| 49 | 'br\} |
43 | 'br\} |
| 50 | .\" |
44 | .\" |
| 51 | .\" Escape single quotes in literal strings from groff's Unicode transform. |
45 | .\" Escape single quotes in literal strings from groff's Unicode transform. |
| 52 | .ie \n(.g .ds Aq \(aq |
46 | .ie \n(.g .ds Aq \(aq |
| 53 | .el .ds Aq ' |
47 | .el .ds Aq ' |
| 54 | .\" |
48 | .\" |
| 55 | .\" If the F register is turned on, we'll generate index entries on stderr for |
49 | .\" If the F register is turned on, we'll generate index entries on stderr for |
| 56 | .\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index |
50 | .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index |
| 57 | .\" entries marked with X<> in POD. Of course, you'll have to process the |
51 | .\" entries marked with X<> in POD. Of course, you'll have to process the |
| 58 | .\" output yourself in some meaningful fashion. |
52 | .\" output yourself in some meaningful fashion. |
| 59 | .ie \nF \{\ |
53 | .\" |
|
|
54 | .\" Avoid warning from groff about undefined register 'F'. |
| 60 | . de IX |
55 | .de IX |
| 61 | . tm Index:\\$1\t\\n%\t"\\$2" |
|
|
| 62 | .. |
56 | .. |
| 63 | . nr % 0 |
57 | .nr rF 0 |
| 64 | . rr F |
58 | .if \n(.g .if rF .nr rF 1 |
| 65 | .\} |
59 | .if (\n(rF:(\n(.g==0)) \{ |
| 66 | .el \{\ |
60 | . if \nF \{ |
| 67 | . de IX |
61 | . de IX |
|
|
62 | . tm Index:\\$1\t\\n%\t"\\$2" |
| 68 | .. |
63 | .. |
|
|
64 | . if !\nF==2 \{ |
|
|
65 | . nr % 0 |
|
|
66 | . nr F 2 |
|
|
67 | . \} |
|
|
68 | . \} |
| 69 | .\} |
69 | .\} |
|
|
70 | .rr rF |
| 70 | .\" |
71 | .\" |
| 71 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). |
72 | .\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). |
| 72 | .\" Fear. Run. Save yourself. No user-serviceable parts. |
73 | .\" Fear. Run. Save yourself. No user-serviceable parts. |
| 73 | . \" fudge factors for nroff and troff |
74 | . \" fudge factors for nroff and troff |
| 74 | .if n \{\ |
75 | .if n \{\ |
| … | |
… | |
| 130 | .\} |
131 | .\} |
| 131 | .rm #[ #] #H #V #F C |
132 | .rm #[ #] #H #V #F C |
| 132 | .\" ======================================================================== |
133 | .\" ======================================================================== |
| 133 | .\" |
134 | .\" |
| 134 | .IX Title "GVPE.PROTOCOL 7" |
135 | .IX Title "GVPE.PROTOCOL 7" |
| 135 | .TH GVPE.PROTOCOL 7 "2008-09-01" "2.2" "GNU Virtual Private Ethernet" |
136 | .TH GVPE.PROTOCOL 7 "2015-10-31" "2.25" "GNU Virtual Private Ethernet" |
| 136 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
137 | .\" For nroff, turn off justification. Always turn off hyphenation; it makes |
| 137 | .\" way too many mistakes in technical documents. |
138 | .\" way too many mistakes in technical documents. |
| 138 | .if n .ad l |
139 | .if n .ad l |
| 139 | .nh |
140 | .nh |
| 140 | .SH "The GNU-VPE Protocols" |
141 | .SH "The GNU-VPE Protocols" |
| 141 | .IX Header "The GNU-VPE Protocols" |
142 | .IX Header "The GNU-VPE Protocols" |
| 142 | .SH "Overview" |
143 | .SH "Overview" |
| 143 | .IX Header "Overview" |
144 | .IX Header "Overview" |
| 144 | \&\s-1GVPE\s0 can make use of a number of protocols. One of them is the \s-1GNU\s0 \s-1VPE\s0 |
145 | \&\s-1GVPE\s0 can make use of a number of protocols. One of them is the \s-1GNU VPE\s0 |
| 145 | protocol which is used to authenticate tunnels and send encrypted data |
146 | protocol which is used to authenticate tunnels and send encrypted data |
| 146 | packets. This protocol is described in more detail the second part of this |
147 | packets. This protocol is described in more detail the second part of this |
| 147 | document. |
148 | document. |
| 148 | .PP |
149 | .PP |
| 149 | The first part of this document describes the transport protocols which |
150 | The first part of this document describes the transport protocols which |
| 150 | are used by \s-1GVPE\s0 to send it's data packets over the network. |
151 | are used by \s-1GVPE\s0 to send its data packets over the network. |
| 151 | .SH "PART 1: Transport protocols" |
152 | .SH "PART 1: Transport protocols" |
| 152 | .IX Header "PART 1: Transport protocols" |
153 | .IX Header "PART 1: Transport protocols" |
| 153 | \&\s-1GVPE\s0 offers a wide range of transport protocols that can be used to |
154 | \&\s-1GVPE\s0 offers a wide range of transport protocols that can be used to |
| 154 | interchange data between nodes. Protocols differ in their overhead, speed, |
155 | interchange data between nodes. Protocols differ in their overhead, speed, |
| 155 | reliability, and robustness. |
156 | reliability, and robustness. |
| 156 | .PP |
157 | .PP |
| 157 | The following sections describe each transport protocol in more |
158 | The following sections describe each transport protocol in more |
| 158 | detail. They are sorted by overhead/efficiency, the most efficient |
159 | detail. They are sorted by overhead/efficiency, the most efficient |
| 159 | transport is listed first: |
160 | transport is listed first: |
| 160 | .Sh "\s-1RAW\s0 \s-1IP\s0" |
161 | .SS "\s-1RAW IP\s0" |
| 161 | .IX Subsection "RAW IP" |
162 | .IX Subsection "RAW IP" |
| 162 | This protocol is the best choice, performance-wise, as the minimum |
163 | This protocol is the best choice, performance-wise, as the minimum |
| 163 | overhead per packet is only 38 bytes. |
164 | overhead per packet is only 38 bytes. |
| 164 | .PP |
165 | .PP |
| 165 | It works by sending the \s-1VPN\s0 payload using raw \s-1IP\s0 frames (using the |
166 | It works by sending the \s-1VPN\s0 payload using raw \s-1IP\s0 frames (using the |
| 166 | protocol set by \f(CW\*(C`ip\-proto\*(C'\fR). |
167 | protocol set by \f(CW\*(C`ip\-proto\*(C'\fR). |
| 167 | .PP |
168 | .PP |
| 168 | Using raw \s-1IP\s0 frames has the drawback that many firewalls block \*(L"unknown\*(R" |
169 | Using raw \s-1IP\s0 frames has the drawback that many firewalls block \*(L"unknown\*(R" |
| 169 | protocols, so this transport only works if you have full \s-1IP\s0 connectivity |
170 | protocols, so this transport only works if you have full \s-1IP\s0 connectivity |
| 170 | between nodes. |
171 | between nodes. |
| 171 | .Sh "\s-1ICMP\s0" |
172 | .SS "\s-1ICMP\s0" |
| 172 | .IX Subsection "ICMP" |
173 | .IX Subsection "ICMP" |
| 173 | This protocol offers very low overhead (minimum 42 bytes), and can |
174 | This protocol offers very low overhead (minimum 42 bytes), and can |
| 174 | sometimes tunnel through firewalls when other protocols can not. |
175 | sometimes tunnel through firewalls when other protocols can not. |
| 175 | .PP |
176 | .PP |
| 176 | It works by prepending an \s-1ICMP\s0 header with type \f(CW\*(C`icmp\-type\*(C'\fR and a code |
177 | It works by prepending an \s-1ICMP\s0 header with type \f(CW\*(C`icmp\-type\*(C'\fR and a code |
| … | |
… | |
| 178 | packets look like echo replies, which looks rather strange to network |
179 | packets look like echo replies, which looks rather strange to network |
| 179 | administrators. |
180 | administrators. |
| 180 | .PP |
181 | .PP |
| 181 | This transport should only be used if other transports (i.e. raw \s-1IP\s0) are |
182 | This transport should only be used if other transports (i.e. raw \s-1IP\s0) are |
| 182 | not available or undesirable (due to their overhead). |
183 | not available or undesirable (due to their overhead). |
| 183 | .Sh "\s-1UDP\s0" |
184 | .SS "\s-1UDP\s0" |
| 184 | .IX Subsection "UDP" |
185 | .IX Subsection "UDP" |
| 185 | This is a good general choice for the transport protocol as \s-1UDP\s0 packets |
186 | This is a good general choice for the transport protocol as \s-1UDP\s0 packets |
| 186 | tunnel well through most firewalls and routers, and the overhead per |
187 | tunnel well through most firewalls and routers, and the overhead per |
| 187 | packet is moderate (minimum 58 bytes). |
188 | packet is moderate (minimum 58 bytes). |
| 188 | .PP |
189 | .PP |
| 189 | It should be used if \s-1RAW\s0 \s-1IP\s0 is not available. |
190 | It should be used if \s-1RAW IP\s0 is not available. |
| 190 | .Sh "\s-1TCP\s0" |
191 | .SS "\s-1TCP\s0" |
| 191 | .IX Subsection "TCP" |
192 | .IX Subsection "TCP" |
| 192 | This protocol is a very bad choice, as it not only has high overhead (more |
193 | This protocol is a very bad choice, as it not only has high overhead (more |
| 193 | than 60 bytes), but the transport also retries on it's own, which leads |
194 | than 60 bytes), but the transport also retries on its own, which leads |
| 194 | to congestion when the link has moderate packet loss (as both the \s-1TCP\s0 |
195 | to congestion when the link has moderate packet loss (as both the \s-1TCP\s0 |
| 195 | transport and the tunneled traffic will retry, increasing congestion more |
196 | transport and the tunneled traffic will retry, increasing congestion more |
| 196 | and more). It also has high latency and is quite inefficient. |
197 | and more). It also has high latency and is quite inefficient. |
| 197 | .PP |
198 | .PP |
| 198 | It's only useful when tunneling through firewalls that block better |
199 | It's only useful when tunneling through firewalls that block better |
| … | |
… | |
| 200 | that supports the \s-1CONNECT\s0 method it can be used to tunnel through a web |
201 | that supports the \s-1CONNECT\s0 method it can be used to tunnel through a web |
| 201 | proxy. For this to work, the \f(CW\*(C`tcp\-port\*(C'\fR should be \f(CW443\fR (\f(CW\*(C`https\*(C'\fR), as |
202 | proxy. For this to work, the \f(CW\*(C`tcp\-port\*(C'\fR should be \f(CW443\fR (\f(CW\*(C`https\*(C'\fR), as |
| 202 | most proxies do not allow connections to other ports. |
203 | most proxies do not allow connections to other ports. |
| 203 | .PP |
204 | .PP |
| 204 | It is an abuse of the usage a proxy was designed for, so make sure you are |
205 | It is an abuse of the usage a proxy was designed for, so make sure you are |
| 205 | allowed to use it for \s-1GVPE\s0. |
206 | allowed to use it for \s-1GVPE.\s0 |
| 206 | .PP |
207 | .PP |
| 207 | This protocol also has server and client sides. If the \f(CW\*(C`tcp\-port\*(C'\fR is |
208 | This protocol also has server and client sides. If the \f(CW\*(C`tcp\-port\*(C'\fR is |
| 208 | set to zero, other nodes cannot connect to this node directly. If the |
209 | set to zero, other nodes cannot connect to this node directly. If the |
| 209 | \&\f(CW\*(C`tcp\-port\*(C'\fR is non-zero, the node can act both as a client as well as a |
210 | \&\f(CW\*(C`tcp\-port\*(C'\fR is non-zero, the node can act both as a client as well as a |
| 210 | server. |
211 | server. |
| 211 | .Sh "\s-1DNS\s0" |
212 | .SS "\s-1DNS\s0" |
| 212 | .IX Subsection "DNS" |
213 | .IX Subsection "DNS" |
| 213 | \&\fB\s-1WARNING:\s0\fR Parsing and generating \s-1DNS\s0 packets is rather tricky. The code |
214 | \&\fB\s-1WARNING:\s0\fR Parsing and generating \s-1DNS\s0 packets is rather tricky. The code |
| 214 | almost certainly contains buffer overflows and other, likely exploitable, |
215 | almost certainly contains buffer overflows and other, likely exploitable, |
| 215 | bugs. You have been warned. |
216 | bugs. You have been warned. |
| 216 | .PP |
217 | .PP |
| … | |
… | |
| 222 | traffic even if it doesn't need to transport packets. |
223 | traffic even if it doesn't need to transport packets. |
| 223 | .PP |
224 | .PP |
| 224 | In addition, the same problems as the \s-1TCP\s0 transport also plague this |
225 | In addition, the same problems as the \s-1TCP\s0 transport also plague this |
| 225 | protocol. |
226 | protocol. |
| 226 | .PP |
227 | .PP |
| 227 | It's only use is to tunnel through firewalls that do not allow direct |
228 | Its only use is to tunnel through firewalls that do not allow direct |
| 228 | internet access. Similar to using a \s-1HTTP\s0 proxy (as the \s-1TCP\s0 transport |
229 | internet access. Similar to using a \s-1HTTP\s0 proxy (as the \s-1TCP\s0 transport |
| 229 | does), it uses a local \s-1DNS\s0 server/forwarder (given by the \f(CW\*(C`dns\-forw\-host\*(C'\fR |
230 | does), it uses a local \s-1DNS\s0 server/forwarder (given by the \f(CW\*(C`dns\-forw\-host\*(C'\fR |
| 230 | configuration value) as a proxy to send and receive data as a client, |
231 | configuration value) as a proxy to send and receive data as a client, |
| 231 | and an \f(CW\*(C`NS\*(C'\fR record pointing to the \s-1GVPE\s0 server (as given by the |
232 | and an \f(CW\*(C`NS\*(C'\fR record pointing to the \s-1GVPE\s0 server (as given by the |
| 232 | \&\f(CW\*(C`dns\-hostname\*(C'\fR directive). |
233 | \&\f(CW\*(C`dns\-hostname\*(C'\fR directive). |
| … | |
… | |
| 240 | .IX Header "PART 2: The GNU VPE protocol" |
241 | .IX Header "PART 2: The GNU VPE protocol" |
| 241 | This section, unfortunately, is not yet finished, although the protocol |
242 | This section, unfortunately, is not yet finished, although the protocol |
| 242 | is stable (until bugs in the cryptography are found, which will likely |
243 | is stable (until bugs in the cryptography are found, which will likely |
| 243 | completely change the following description). Nevertheless, it should give |
244 | completely change the following description). Nevertheless, it should give |
| 244 | you some overview over the protocol. |
245 | you some overview over the protocol. |
| 245 | .Sh "Anatomy of a \s-1VPN\s0 packet" |
246 | .SS "Anatomy of a \s-1VPN\s0 packet" |
| 246 | .IX Subsection "Anatomy of a VPN packet" |
247 | .IX Subsection "Anatomy of a VPN packet" |
| 247 | The exact layout and field lengths of a \s-1VPN\s0 packet is determined at |
248 | The exact layout and field lengths of a \s-1VPN\s0 packet is determined at |
| 248 | compile time and doesn't change. The same structure is used for all |
249 | compile time and doesn't change. The same structure is used for all |
| 249 | transport protocols, be it \s-1RAWIP\s0 or \s-1TCP\s0. |
250 | transport protocols, be it \s-1RAWIP\s0 or \s-1TCP.\s0 |
| 250 | .PP |
251 | .PP |
| 251 | .Vb 3 |
252 | .Vb 3 |
| 252 | \& +\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+ |
253 | \& +\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+ |
| 253 | \& | HMAC | TYPE | SRCDST | DATA | |
254 | \& | HMAC | TYPE | SRCDST | DATA | |
| 254 | \& +\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+ |
255 | \& +\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+ |
| 255 | .Ve |
256 | .Ve |
| 256 | .PP |
257 | .PP |
| 257 | The \s-1HMAC\s0 field is present in all packets, even if not used (e.g. in auth |
258 | The \s-1HMAC\s0 field is present in all packets, even if not used (e.g. in auth |
| 258 | request packets), in which case it is set to all zeroes. The checksum |
259 | request packets), in which case it is set to all zeroes. The \s-1MAC\s0 itself is |
| 259 | itself is calculated over the \s-1TYPE\s0, \s-1SRCDST\s0 and \s-1DATA\s0 fields in all cases. |
260 | calculated over the \s-1TYPE, SRCDST\s0 and \s-1DATA\s0 fields in all cases. |
| 260 | .PP |
261 | .PP |
| 261 | The \s-1TYPE\s0 field is a single byte and determines the purpose of the packet |
262 | The \s-1TYPE\s0 field is a single byte and determines the purpose of the packet |
| 262 | (e.g. \s-1RESET\s0, \s-1COMPRESSED/UNCOMPRESSED\s0 \s-1DATA\s0, \s-1PING\s0, \s-1AUTH\s0 \s-1REQUEST/RESPONSE\s0, |
263 | (e.g. \s-1RESET, COMPRESSED/UNCOMPRESSED DATA, PING, AUTH REQUEST/RESPONSE, |
| 263 | \&\s-1CONNECT\s0 \s-1REQUEST/INFO\s0 etc.). |
264 | CONNECT REQUEST/INFO\s0 etc.). |
| 264 | .PP |
265 | .PP |
| 265 | \&\s-1SRCDST\s0 is a three byte field which contains the source and destination |
266 | \&\s-1SRCDST\s0 is a three byte field which contains the source and destination |
| 266 | node IDs (12 bits each). |
267 | node IDs (12 bits each). |
| 267 | .PP |
268 | .PP |
| 268 | The \s-1DATA\s0 portion differs between each packet type, naturally, and is the |
269 | The \s-1DATA\s0 portion differs between each packet type, naturally, and is the |
| 269 | only part that can be encrypted. Data packets contain more fields, as |
270 | only part that can be encrypted. Data packets contain more fields, as |
| 270 | shown: |
271 | shown: |
| 271 | .PP |
272 | .PP |
| 272 | .Vb 3 |
273 | .Vb 3 |
| 273 | \& +\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-+ |
274 | \& +\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-+ |
| 274 | \& | HMAC | TYPE | SRCDST | RAND | SEQNO | DATA | |
275 | \& | HMAC | TYPE | SRCDST | SEQNO | DATA | |
| 275 | \& +\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-+ |
276 | \& +\-\-\-\-\-\-+\-\-\-\-\-\-+\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-+\-\-\-\-\-\-+ |
| 276 | .Ve |
277 | .Ve |
| 277 | .PP |
278 | .PP |
| 278 | \&\s-1RAND\s0 is a sequence of fully random bytes, used to increase the entropy of |
|
|
| 279 | the data for encryption purposes. |
|
|
| 280 | .PP |
|
|
| 281 | \&\s-1SEQNO\s0 is a 32\-bit sequence number. It is negotiated at every connection |
279 | \&\s-1SEQNO\s0 is a 32\-bit sequence number. It is negotiated at every connection |
| 282 | initialization and starts at some random 31 bit value. \s-1VPE\s0 currently uses |
280 | initialization and starts at some random 31 bit value. \s-1GVPE\s0 currently uses |
| 283 | a sliding window of 512 packets/sequence numbers to detect reordering, |
281 | a sliding window of 512 packets/sequence numbers to detect reordering, |
| 284 | duplication and replay attacks. |
282 | duplication and replay attacks. |
|
|
283 | .PP |
|
|
284 | The encryption is done on \s-1SEQNO+DATA\s0 in \s-1CTR\s0 mode with \s-1IV\s0 generated from |
|
|
285 | the seqno (for \s-1AES:\s0 seqno || seqno || seqno || (u32)0), which ensures |
|
|
286 | uniqueness for a given key. |
| 285 | .Sh "The authentication protocol" |
287 | .SS "The authentication/key exchange protocol" |
| 286 | .IX Subsection "The authentication protocol" |
288 | .IX Subsection "The authentication/key exchange protocol" |
| 287 | Before nodes can exchange packets, they need to establish authenticity of |
289 | Before nodes can exchange packets, they need to establish authenticity of |
| 288 | the other side and a key. Every node has a private \s-1RSA\s0 key and the public |
290 | the other side and a key. Every node has a private \s-1RSA\s0 key and the public |
| 289 | \&\s-1RSA\s0 keys of all other nodes. |
291 | \&\s-1RSA\s0 keys of all other nodes. |
| 290 | .PP |
292 | .PP |
| 291 | A host establishes a simplex connection by sending the other node an |
293 | When a node wants to establish a connection to another node, it sends an |
| 292 | \&\s-1RSA\s0 encrypted challenge containing a random challenge (consisting of |
294 | RSA-OEAP-encrypted challenge and an \s-1ECDH \s0(curve25519) key. The other node |
| 293 | the encryption key to use when sending packets, more random data and |
295 | replies with its own \s-1ECDH\s0 key and a \s-1HKDF\s0 of the challenge and both \s-1ECDH\s0 |
| 294 | \&\s-1PKCS1_OAEP\s0 padding) and a random 16 byte \*(L"challenge-id\*(R" (used to detect |
296 | keys to prove its identity. |
| 295 | duplicate auth packets). The destination node will respond by replying |
|
|
| 296 | with an (unencrypted) \s-1RIPEMD160\s0 hash of the decrypted challenge, which |
|
|
| 297 | will authenticate that node. The destination node will also set the |
|
|
| 298 | outgoing encryption parameters as given in the packet. |
|
|
| 299 | .PP |
297 | .PP |
| 300 | When the source node receives a correct auth reply (by verifying the |
298 | The remote node enganges in exactly the same protocol. When both nodes |
| 301 | hash and the id, which will expire after 120 seconds), it will start to |
299 | have exchanged their challenge and verified the response, they calculate a |
| 302 | accept data packets from the destination node. |
300 | cipher key and a \s-1HMAC\s0 key and start exchanging data packets. |
| 303 | .PP |
301 | .PP |
| 304 | This means that a node can only initiate a simplex connection, telling the |
302 | In detail, the challenge consist of: |
| 305 | other side the key it has to use when it sends packets. The challenge |
|
|
| 306 | reply is only used to set the current \s-1IP\s0 address of the other side and |
|
|
| 307 | protocol parameters. |
|
|
| 308 | .PP |
303 | .PP |
| 309 | This protocol is completely symmetric, so to be able to send packets the |
304 | .Vb 1 |
| 310 | destination node must send a challenge in the exact same way as already |
305 | \& RSA\-OAEP (SEQNO MAC CIPHER SALT EXTRA\-AUTH) ECDH1 |
| 311 | described (so, in essence, two simplex connections are created per node |
306 | .Ve |
| 312 | pair). |
307 | .PP |
|
|
308 | That is, it encrypts (with the public key of the remote node) an initial |
|
|
309 | sequence number for data packets, key material for the \s-1HMAC\s0 key, key |
|
|
310 | material for the cipher key, a salt used by the \s-1HKDF \s0(as shown later) and |
|
|
311 | some extra random bytes that are unused except for authentication. It also |
|
|
312 | sends the public key of a curve25519 exchange. |
|
|
313 | .PP |
|
|
314 | The remote node decrypts the \s-1RSA\s0 data, generates its own \s-1ECDH\s0 key (\s-1ECDH2\s0), |
|
|
315 | and replies with: |
|
|
316 | .PP |
|
|
317 | .Vb 1 |
|
|
318 | \& HKDF\-Expand (HKDF\-Extract (ECDH2, RSA), ECDH1, AUTH_DIGEST_SIZE) ECDH2 |
|
|
319 | .Ve |
|
|
320 | .PP |
|
|
321 | That is, it extracts from the decrypted \s-1RSA\s0 challenge, using its \s-1ECDH\s0 |
|
|
322 | key as salt, and then expands using the requesting node's \s-1ECDH1\s0 key. The |
|
|
323 | resulting hash is returned as a proof that the node could decrypt the \s-1RSA\s0 |
|
|
324 | challenge data, together with the \s-1ECDH\s0 key. |
|
|
325 | .PP |
|
|
326 | After both nodes have done this to each other, they calculate the shared |
|
|
327 | \&\s-1ECDH\s0 secret, cipher and \s-1HMAC\s0 keys for the session (each node generates two |
|
|
328 | cipher and \s-1HMAC\s0 keys, one for sending and one for receiving). |
|
|
329 | .PP |
|
|
330 | The \s-1HMAC\s0 key for sending is generated as follow: |
|
|
331 | .PP |
|
|
332 | .Vb 1 |
|
|
333 | \& HMAC_KEY = HKDF\-Expand (HKDF\-Extract (REMOTE_SALT, MAC ECDH_SECRET), info, HMAC_MD_SIZE) |
|
|
334 | .Ve |
|
|
335 | .PP |
|
|
336 | It extracts from \s-1MAC\s0 and \s-1ECDH_SECRET\s0 using the \fIremote\fR \s-1SALT,\s0 then |
|
|
337 | expands using a static info string. |
|
|
338 | .PP |
|
|
339 | The cipher key is generated in the same way, except using the \s-1CIPHER\s0 part |
|
|
340 | of the original challenge. |
|
|
341 | .PP |
|
|
342 | The result of this process is to authenticate each node to the other |
|
|
343 | node, while exchanging keys using both \s-1RSA\s0 and \s-1ECDH,\s0 the latter providing |
|
|
344 | perfect forward secrecy. |
|
|
345 | .PP |
|
|
346 | The protocol has been overdesigned where this was possible without |
|
|
347 | increasing implementation complexity, in an attempt to protect against |
|
|
348 | implementation or protocol failures. For example, if the \s-1ECDH\s0 challenge |
|
|
349 | was found to be flawed, perfect forward secrecy would be lost, but the |
|
|
350 | data would likely still be protected. Likewise, standard algorithms and |
|
|
351 | implementations are used where possible. |
| 313 | .Sh "Retrying" |
352 | .SS "Retrying" |
| 314 | .IX Subsection "Retrying" |
353 | .IX Subsection "Retrying" |
| 315 | When there is no response to an auth request, the node will send auth |
354 | When there is no response to an auth request, the node will send auth |
| 316 | requests in bursts with an exponential back-off. After some time it will |
355 | requests in bursts with an exponential back-off. After some time it will |
| 317 | resort to \s-1PING\s0 packets, which are very small (8 bytes + protocol header) |
356 | resort to \s-1PING\s0 packets, which are very small (8 bytes + protocol header) |
| 318 | and lightweight (no \s-1RSA\s0 operations required). A node that receives ping |
357 | and lightweight (no \s-1RSA\s0 operations required). A node that receives ping |
| … | |
… | |
| 332 | period to \f(CW\*(C`max\-ttl\*(C'\fR seconds. |
371 | period to \f(CW\*(C`max\-ttl\*(C'\fR seconds. |
| 333 | .PP |
372 | .PP |
| 334 | Sending packets over the \s-1VPN\s0 will reset the retry intervals as well, which |
373 | Sending packets over the \s-1VPN\s0 will reset the retry intervals as well, which |
| 335 | means as long as somebody is trying to send packets to a given node, \s-1GVPE\s0 |
374 | means as long as somebody is trying to send packets to a given node, \s-1GVPE\s0 |
| 336 | will try to connect every few seconds. |
375 | will try to connect every few seconds. |
| 337 | .Sh "Routing and Protocol translation" |
376 | .SS "Routing and Protocol translation" |
| 338 | .IX Subsection "Routing and Protocol translation" |
377 | .IX Subsection "Routing and Protocol translation" |
| 339 | The \s-1GVPE\s0 routing algorithm is easy: there isn't much routing to speak |
378 | The \s-1GVPE\s0 routing algorithm is easy: there isn't much routing to speak |
| 340 | of: When routing packets to another node, \s-1GVPE\s0 trues the following |
379 | of: When routing packets to another node, \s-1GVPE\s0 tries the following |
| 341 | options, in order: |
380 | options, in order: |
| 342 | .IP "If the two nodes should be able to reach each other directly (common protocol, port known), then \s-1GVPE\s0 will send the packet directly to the other node." 4 |
381 | .IP "If the two nodes should be able to reach each other directly (common protocol, port known), then \s-1GVPE\s0 will send the packet directly to the other node." 4 |
| 343 | .IX Item "If the two nodes should be able to reach each other directly (common protocol, port known), then GVPE will send the packet directly to the other node." |
382 | .IX Item "If the two nodes should be able to reach each other directly (common protocol, port known), then GVPE will send the packet directly to the other node." |
| 344 | .PD 0 |
383 | .PD 0 |
| 345 | .ie n .IP "If this isn't possible (e.g. because the node doesn't have a \*(C`hostname\*(C' or known port), but the nodes speak a common protocol and a router is available, then \s-1GVPE\s0 will ask a router to ""mediate"" between both nodes (see below)." 4 |
384 | .ie n .IP "If this isn't possible (e.g. because the node doesn't have a \*(C`hostname\*(C' or known port), but the nodes speak a common protocol and a router is available, then \s-1GVPE\s0 will ask a router to ""mediate"" between both nodes (see below)." 4 |
| 346 | .el .IP "If this isn't possible (e.g. because the node doesn't have a \f(CW\*(C`hostname\*(C'\fR or known port), but the nodes speak a common protocol and a router is available, then \s-1GVPE\s0 will ask a router to ``mediate'' between both nodes (see below)." 4 |
385 | .el .IP "If this isn't possible (e.g. because the node doesn't have a \f(CW\*(C`hostname\*(C'\fR or known port), but the nodes speak a common protocol and a router is available, then \s-1GVPE\s0 will ask a router to ``mediate'' between both nodes (see below)." 4 |
| 347 | .IX Item "If this isn't possible (e.g. because the node doesn't have a hostname or known port), but the nodes speak a common protocol and a router is available, then GVPE will ask a router to mediate between both nodes (see below)." |
386 | .IX Item "If this isn't possible (e.g. because the node doesn't have a hostname or known port), but the nodes speak a common protocol and a router is available, then GVPE will ask a router to mediate between both nodes (see below)." |
| 348 | .ie n .IP "If a direct connection isn't possible (no common protocols) or forbidden (\*(C`deny\-direct\*(C'\fR) and there are any routers, then \s-1GVPE\s0 will try to send packets to the router with the highest priority that is connected already \fIand is able (as specified by the config file) to connect directly to the target node." 4 |
387 | .ie n .IP "If a direct connection isn't possible (no common protocols) or forbidden (\*(C`deny\-direct\*(C') and there are any routers, then \s-1GVPE\s0 will try to send packets to the router with the highest priority that is connected already \fIand\fR is able (as specified by the config file) to connect directly to the target node." 4 |
| 349 | .el .IP "If a direct connection isn't possible (no common protocols) or forbidden (\f(CW\*(C`deny\-direct\*(C'\fR) and there are any routers, then \s-1GVPE\s0 will try to send packets to the router with the highest priority that is connected already \fIand\fR is able (as specified by the config file) to connect directly to the target node." 4 |
388 | .el .IP "If a direct connection isn't possible (no common protocols) or forbidden (\f(CW\*(C`deny\-direct\*(C'\fR) and there are any routers, then \s-1GVPE\s0 will try to send packets to the router with the highest priority that is connected already \fIand\fR is able (as specified by the config file) to connect directly to the target node." 4 |
| 350 | .IX Item "If a direct connection isn't possible (no common protocols) or forbidden (deny-direct) and there are any routers, then GVPE will try to send packets to the router with the highest priority that is connected already and is able (as specified by the config file) to connect directly to the target node." |
389 | .IX Item "If a direct connection isn't possible (no common protocols) or forbidden (deny-direct) and there are any routers, then GVPE will try to send packets to the router with the highest priority that is connected already and is able (as specified by the config file) to connect directly to the target node." |
| 351 | .IP "If no such router exists, then \s-1GVPE\s0 will simply send the packet to the node with the highest priority available." 4 |
390 | .IP "If no such router exists, then \s-1GVPE\s0 will simply send the packet to the node with the highest priority available." 4 |
| 352 | .IX Item "If no such router exists, then GVPE will simply send the packet to the node with the highest priority available." |
391 | .IX Item "If no such router exists, then GVPE will simply send the packet to the node with the highest priority available." |
| 353 | .IP "Failing all that, the packet will be dropped." 4 |
392 | .IP "Failing all that, the packet will be dropped." 4 |
| 354 | .IX Item "Failing all that, the packet will be dropped." |
393 | .IX Item "Failing all that, the packet will be dropped." |
| 355 | .PD |
394 | .PD |
| 356 | .PP |
395 | .PP |
| 357 | A host can usually declare itself unreachable directly by setting it's |
396 | A host can usually declare itself unreachable directly by setting its |
| 358 | port number(s) to zero. It can declare other hosts as unreachable by using |
397 | port number(s) to zero. It can declare other hosts as unreachable by using |
| 359 | a config-file that disables all protocols for these other hosts. Another |
398 | a config-file that disables all protocols for these other hosts. Another |
| 360 | option is to disable all protocols on that host in the other config files. |
399 | option is to disable all protocols on that host in the other config files. |
| 361 | .PP |
400 | .PP |
| 362 | If two hosts cannot connect to each other because their \s-1IP\s0 address(es) |
401 | If two hosts cannot connect to each other because their \s-1IP\s0 address(es) |
| … | |
… | |
| 368 | connection to the other peer, which is usually possible even when both |
407 | connection to the other peer, which is usually possible even when both |
| 369 | hosts are behind a \s-1NAT\s0 gateway. |
408 | hosts are behind a \s-1NAT\s0 gateway. |
| 370 | .PP |
409 | .PP |
| 371 | Routing via other nodes works because the \s-1SRCDST\s0 field is not encrypted, |
410 | Routing via other nodes works because the \s-1SRCDST\s0 field is not encrypted, |
| 372 | so the router can just forward the packet to the destination host. Since |
411 | so the router can just forward the packet to the destination host. Since |
| 373 | each host uses it's own private key, the router will not be able to |
412 | each host uses its own private key, the router will not be able to |
| 374 | decrypt or encrypt packets, it will just act as a simple router and |
413 | decrypt or encrypt packets, it will just act as a simple router and |
| 375 | protocol translator. |
414 | protocol translator. |
