VaulTor: Putting the TEE in Tor
Humza Ikram, Rumaisa Habib, Muaz Ali, Zartash Afzal Uzmi
TL;DR
VaulTor addresses the risk of deanonymizing Hidden Services on Tor by introducing a vault as a new trusted actor that hosts HS content inside a Trusted Execution Environment, thereby reducing the HS provider’s uptime requirements and exposure. The approach preserves client anonymity and maintains Tor’s latency characteristics while enabling dynamic content and backward compatibility, using a Vault Contact Hidden Service and a Host Program running within an enclave. The authors provide a detailed protocol for HP creation and bootstrapping, a rigorous threat model, and an evaluation showing only modest performance overhead ($ ext{TTFB}$ up to $5.7\%$, $ ext{TTLB}$ up to $2.9\%$) in real Tor scenarios. They also discuss deployment strategies, incentives, and privacy considerations, arguing that TEEs offer robust protection against a range of attacks and can adapt to future TEE technologies, making VaulTor a practical path toward stronger HS anonymity with minimal client-impact.
Abstract
Online services that desire to operate anonymously routinely host themselves as 'Hidden Services' in the Tor network. However, these services are frequently threatened by deanonymization attacks, whereby their IP address and location may be inferred by the authorities. We present VaulTor, a novel architecture for the Tor network to ensure an extra layer of security for the Hidden Services against deanonymization attacks. In this new architecture, a volunteer (vault) is incentivized to host the web application content on behalf of the Hidden Service. The vault runs the hosted application in a Trusted Execution Environment (TEE) and becomes the point of contact for interested clients. This setup can substantially reduce the uptime requirement of the original Hidden Service provider and hence significantly decrease the chance of deanonymization attacks against them. We also show that the VaulTor architecture does not cause any noticeable performance degradation in accessing the hosted content (the performance degradation ranges from 2.6-5.5%).
