2018 IEEE Symposium on Security and Privacy (SP) 2018
DOI: 10.1109/sp.2018.00021
|View full text |Cite
|
Sign up to set email alerts
|

A Formal Treatment of Accountable Proxying Over TLS

Abstract: Much of Internet traffic nowadays passes through active proxies, whose role is to inspect, filter, cache, or transform data exchanged between two endpoints. To perform their tasks, such proxies modify channel-securing protocols, like TLS, resulting in serious vulnerabilities. Such problems are exacerbated by the fact that middleboxes are often invisible to one or both endpoints, leading to a lack of accountability. A recent protocol, called mcTLS, pioneered accountability for proxies, which are authorized by t… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
15
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 20 publications
(15 citation statements)
references
References 28 publications
(42 reference statements)
0
15
0
Order By: Relevance
“…mcTLS allows TLS endpoints (i.e., clients and webservers) to introduce middleboxes in secure end-to-end connection while restricting what the middleboxes can read or write. However, Bhargavan et al [9] show that mcTLS is insecure and susceptible to a class of attack called middlebox confusion attacks. They suggested a provable secure alternative to mcTLS avoiding the middlebox confusion issue.…”
Section: Delegation and Multi-entity Communication In Other Protocolsmentioning
confidence: 99%
“…mcTLS allows TLS endpoints (i.e., clients and webservers) to introduce middleboxes in secure end-to-end connection while restricting what the middleboxes can read or write. However, Bhargavan et al [9] show that mcTLS is insecure and susceptible to a class of attack called middlebox confusion attacks. They suggested a provable secure alternative to mcTLS avoiding the middlebox confusion issue.…”
Section: Delegation and Multi-entity Communication In Other Protocolsmentioning
confidence: 99%
“…Multi-Context TLS [16] was developed to solve this issue. However, the protocol is insecure [17] and it provides neither flow-based encryption nor SFC isolation. Hence, another approach to this problem is to enable the NFV infrastructure to provide hop by hop encryption and automatically exchange keys and set up secure channels between the VNFs.…”
Section: Related Workmentioning
confidence: 99%
“…erefore, the client should fully trust the proxy. mcTLS may be weak in several cases, for example, Poisoning Caches with an Unknown Key Share Attack [57]. Furthermore, mcTLS complicates the TLS protocol by making significant changes to the handshake protocol, and Security and Communication Networks the sizes of the handshake messages are significantly large.…”
Section: Multicontext Tlsmentioning
confidence: 99%