In computer networking, tcpcrypt is a transport layer communication encryption protocol.[1][2] Unlike prior protocols like TLS (SSL), tcpcrypt is implemented as a TCP extension. It was designed by a team of six security and networking experts: Andrea Bittau, Mike Hamburg, Mark Handley, David Mazières, Dan Boneh and Quinn Slack.[3] Tcpcrypt has been published as an Internet Draft.[4] Experimental user-space implementations are available for Linux, Mac OS X, FreeBSD and Windows. There is also a Linux kernel implementation.
| Original author(s) | Andrea Bittau, Mike Hamburg, Mark Handley, David Mazières, Dan Boneh and Quinn Slack. |
|---|---|
| Type | communication encryption protocol |
| Website | tcpcrypt |
The TCPINC (TCP Increased Security) working group was formed in June 2014 by IETF to work on standardizing security extensions in the TCP protocol.[5] In May 2019 the working group released RFC 8547 and RFC 8548 as an experimental standard for Tcpcrypt.
Description
editTcpcrypt provides opportunistic encryption — if either side does not support this extension, then the protocol falls back to regular unencrypted TCP. Tcpcrypt also provides encryption to any application using TCP, even ones that do not know about encryption. This enables incremental and seamless deployment.[6]
Unlike TLS, tcpcrypt itself does not do any authentication, but passes a unique "session ID" down to the application; the application can then use this token for further authentication. This means that any authentication scheme can be used, including passwords or certificates. It also does a larger part of the public-key connection initiation on the client side, to reduce load on servers and mitigate DoS attacks.[6]
History
editThe first draft of the protocol specification was published in July 2010, with reference implementations following in August. However, after initial meetings in IETF, proponents of the protocol failed to gain traction for standardization and the project went dormant in 2011.[7]
In 2013 and 2014, following Edward Snowden's Global surveillance disclosures about the NSA and agencies of other governments, IETF took a strong stance for protecting Internet users against surveillance.[8][9] This aligns with tcpcrypt's goals of ubiquitous transparent encryption, which revived interest in standardization of the protocol. An official IETF mailing list was created for tcpcrypt in March 2014,[10] followed by the formation of the TCPINC (TCP Increased Security) working group in June[5] and a new version of the draft specification.
Performance
editTcpcrypt enforces TCP timestamps and adds its own TCP options to each data packet, amounting to 36 bytes per packet compared to plain TCP. With a mean observed packet size for TCP packets of 471 bytes,[11] this can lead to an overhead of 8% of useful bandwidth. This 36 bytes overhead may not be an issue for internet connections faster than 64kbs but it can be an issue for dial-up internet users.
Compared to TLS/SSL, tcpcrypt is designed to have a lower performance impact. In part this is because tcpcrypt does not have built-in authentication, which can be implemented by the application itself. Cryptography primitives are used in such a way to reduce load on the server side, because a single server usually has to provide services for far more clients than the reverse.[6]
Implementations
editThe current user space implementations are considered experimental and are reportedly unstable on some systems. It also does not support IPv6 yet, which is currently only supported by the Linux kernel version. It is expected that once tcpcrypt becomes a standard, operating systems will come with tcpcrypt support built-in, making the user space solution unnecessary.[citation needed]
See also
edit- DTLS
- IPsec
- Obfuscated TCP – an earlier failed proposal for opportunistic TCP encryption
References
edit- ^ Andrea Bittau; et al. (2010-08-13). The case for ubiquitous transport-level encryption (PDF). 19th USENIX Security Symposium.
- ^ Michael Cooney (2010-07-19). "Is ubiquitous encryption technology on the horizon?". Network World.
- ^ "tcpcrypt – About us". tcpcrypt.org.
- ^ Bittau, A.; D. Boneh; M. Hamburg; M. Handley; D. Mazieres; Q. Slack (21 July 2014). Cryptographic protection of TCP Streams (tcpcrypt). IETF. I-D draft-bittau-tcpinc-01.
- ^ a b "TCP Increased Security (tcpinc)". Charter for Working Group. Retrieved 25 July 2014.
- ^ a b c Jake Edge (2010-08-25). "Transport-level encryption with Tcpcrypt". LWN.net.
- ^ Mark Handley (9 September 2013). "Kernel patch for Linux 3.10.10?" (Mailing list).
Two years ago we failed to get much traction for the takeup of tcpcrypt.
- ^ Richard Chirgwin (14 May 2014). "IETF plans to NSA-proof all future internet protocols". The Register.
- ^ Mark Jackson (13 May 2014). "IETF Commits to Hamper State Sponsored Mass Internet Surveillance". ISP Review.
- ^ "New Non-WG Mailing List: Tcpcrypt -- Discussion list for adding encryption to TCP" (Mailing list). IETF Secretariat. 24 March 2014.
- ^ "Sean McCreary and kc klaffy". "Trends in Wide Area IP Traffic Patterns A View from Ames Internet Exchange".