RAPTEE: Leveraging trusted execution environments for Byzantine-tolerant peer sampling services
Peer sampling is a first-class abstraction used in distributed systems for overlay management and information dissemination. The goal of peer sampling is to continuously build and refresh a partial and local view of the full membership of a dynamic, large-scale distributed system. Malicious nodes un...
Gespeichert in:
Hauptverfasser: | , , , , , |
---|---|
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | Peer sampling is a first-class abstraction used in distributed systems for
overlay management and information dissemination. The goal of peer sampling is
to continuously build and refresh a partial and local view of the full
membership of a dynamic, large-scale distributed system. Malicious nodes under
the control of an adversary may aim at being over-represented in the views of
correct nodes, increasing their impact on the proper operation of protocols
built over peer sampling. State-of-the-art Byzantine resilient peer sampling
protocols reduce this bias as long as Byzantines are not overly present. This
paper studies the benefits brought to the resilience of peer sampling services
when considering that a small portion of trusted nodes can run code whose
authenticity and integrity can be assessed within a trusted execution
environment, and specifically Intel's software guard extensions technology
(SGX). We present RAPTEE, a protocol that builds and leverages trusted
gossip-based communications to hamper an adversary's ability to increase its
system-wide representation in the views of all nodes. We apply RAPTEE to
BRAHMS, the most resilient peer sampling protocol to date. Experiments with
10,000 nodes show that with only 1% of SGX-capable devices, RAPTEE can reduce
the proportion of Byzantine IDs in the view of honest nodes by up to 17% when
the system contains 10% of Byzantine nodes. In addition, the security
guarantees of RAPTEE hold even in the presence of a powerful attacker
attempting to identify trusted nodes and injecting view-poisoned trusted nodes. |
---|---|
DOI: | 10.48550/arxiv.2203.04258 |