mirror of
https://github.com/tailscale/tailscale.git
synced 2024-11-26 03:25:35 +00:00
02ad987e24
This is so that we can plumb our client capability version through the protocol as the Noise version. The capability version increments more frequently than strictly required (the Noise version only needs to change when cryptographically-significant changes are made to the protocol, whereas the capability version also indicates changes in non-cryptographically-significant parts of the protocol), but this gives us a safe pre-auth way to determine if the client supports future protocol features, while still relying on Noise's strong assurance that the client and server have agreed on the same version. Currently, the server executes the same protocol regardless of the version number, and just presents the version to the caller so they can do capability-based things in the upper RPC protocol. In future, we may add a ratchet to disallow obsolete protocols, or vary the Noise handshake behavior based on requested version. Updates #3488 Signed-off-by: David Anderson <danderson@tailscale.com> |
||
|---|---|---|
| .. | ||
| auto.go | ||
| client.go | ||
| controlclient_test.go | ||
| debug_test.go | ||
| debug.go | ||
| direct_test.go | ||
| direct.go | ||
| map_test.go | ||
| map.go | ||
| noise_test.go | ||
| noise.go | ||
| sign_supported_test.go | ||
| sign_supported.go | ||
| sign_unsupported.go | ||
| sign.go | ||
| status.go | ||