Encrypt TCP tunnel payload with AES-GCM #6
No reviewers
Labels
No labels
blocked
bug
draft
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
s1d3sw1ped/teleport!6
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/teleport-2-tcp-gcm"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #2
Severity: High
TCP
forwardDatacopied the payload in the clear after the AES-GCM handshake. UDP was already encrypted per datagram; README claimed all traffic is AES-GCM.What changed
uint32length + ciphertext. Reader caps length, decrypts, writes plaintext.forwardDataimplementations (internal/clientandinternal/server), both directions of the tunnel (encrypt onto the tunnel, decrypt off it).Tests
forwardDatacovered in both directions.Do not merge from this bot.