Skip to main navigation Skip to search Skip to main content

Multi-Context TLS (mcTLS): Enabling Secure In-Network Functionality in TLS

  • David Naylor
  • , Kyle Schomp
  • , Matteo Varvello
  • , Ilias Leontiadis
  • , Jeremy Blackburn
  • , Diego R. López
  • , Konstantina Papagiannaki
  • , Pablo Rodriguez Rodriguez
  • , Peter Steenkiste
  • Carnegie Mellon University
  • Case Western Reserve University
  • Telefonica

Research output: Contribution to journalArticlepeer-review

49 Scopus citations

Abstract

A significant fraction of Internet traffic is now encrypted and HTTPS will likely be the default in HTTP/2. However, Transport Layer Security (TLS), the standard protocol for encryption in the Internet, assumes that all functionality resides at the endpoints, making it impossible to use in-network services that optimize network resource usage, improve user experience, and protect clients and servers from security threats. Re-introducing in-network functionality into TLS sessions today is done through hacks, often weakening overall security. In this paper we introduce multi-context TLS (mcTLS), which extends TLS to support middleboxes. mcTLS breaks the current "all-or-nothing" security model by allowing endpoints and content providers to explicitly introduce middleboxes in secure end-to-end sessions while controlling which parts of the data they can read or write. We evaluate a prototype mcTLS implementation in both controlled and "live" experiments, showing that its benefits come at the cost of minimal overhead. More importantly, we show that mcTLS can be incrementally deployed and requires only small changes to client, server, and middlebox software.

Original languageEnglish
Pages (from-to)199-212
Number of pages14
JournalComputer Communication Review
Volume45
Issue number4
DOIs
StatePublished - Aug 17 2015

Keywords

  • Https
  • Ssl
  • Tls

Fingerprint

Dive into the research topics of 'Multi-Context TLS (mcTLS): Enabling Secure In-Network Functionality in TLS'. Together they form a unique fingerprint.

Cite this