Secure routing strategies in DHT-based systems
Globe'10 Proceedings of the Third international conference on Data management in grid and peer-to-peer systems
Load balanced scalable Byzantine agreement through quorum building, with full information
ICDCN'11 Proceedings of the 12th international conference on Distributed computing and networking
Commensal cuckoo: secure group partitioning for large-scale services
ACM SIGOPS Operating Systems Review
Resource-competitive analysis: a new perspective on attack-resistant distributed computing
FOMC '12 Proceedings of the 8th International Workshop on Foundations of Mobile Computing
Adding query privacy to robust DHTs
Proceedings of the 7th ACM Symposium on Information, Computer and Communications Security
Towards practical communication in Byzantine-resistant DHTs
IEEE/ACM Transactions on Networking (TON)
| Hi-index | 0.00 |
There are several analytical results on distributed hash tables (DHTs) that can tolerate Byzantine faults. Unfortunately, in such systems, operations such as data retrieval and message sending incur significant communication costs. For example, a simple scheme used in many Byzantine fault-tolerant DHT constructions of $n$ nodes requires $O(\log^{3}n)$ messages, this is likely impractical for real-world applications. The previous best known message complexity is $O(\log^2{n})$ {\it in expectation}, however, the corresponding protocol suffers from prohibitive costs owing to hidden constants in the asymptotic notation and setup costs. In this paper, we focus on reducing the communication costs against a computationally bounded adversary. We employ threshold cryptography and distributed key generation to define two protocols both of which are more efficient than existing solutions. In comparison, our first protocol is {\it deterministic} with $O(\log^2{}n)$ message complexity and our second protocol is randomized with expected $O(\log{n})$ message complexity. Further, both the hidden constants and setup costs for our protocols are small and no trusted third party is required. Finally, we present results from micro benchmarks conducted over PlanetLab showing that our protocols are practical for deployment under significant levels of churn and adversarial behaviour.