TheArchive/tailscale
1
0
Fork 0
mirror of https://github.com/tailscale/tailscale.git synced 2024-12-04 07:25:39 +00:00
Code Issues Packages Projects Releases Wiki Activity

disco: amplify comment that disco ping's NodeKey shouldn't be trusted by itself.

Browse Source 
Signed-off-by: David Anderson <danderson@tailscale.com>
(cherry picked from commit 1c56643136)
This commit is contained in:
David Anderson 2021-10-18 10:50:13 -07:00 committed by Brad Fitzpatrick
parent 4a531a0aed
commit ae267e0df1
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
disco/disco.go
View File

@ -110,11 +110,12 @@ type Ping struct {
// TxID is a random client-generated per-ping transaction ID.
TxID [12]byte
// NodeKey is the ping sender's wireguard public key. Old
// clients (~1.16.0 and earlier) don't send this field. It
// shouldn't be trusted by itself. But if present and the
// netmap's peer for this NodeKey's DiscoKey matches the
// sender of this disco key, they it can be.
// NodeKey is allegedly the ping sender's wireguard public key.
// Old clients (~1.16.0 and earlier) don't send this field.
// It shouldn't be trusted by itself, but can be combined with
// netmap data to reduce the discokey:nodekey relation from 1:N to
// 1:1.
NodeKey tailcfg.NodeKey
}