Key Infection: Smart Trust for Smart Dust
Date: October 2004
Publication: Proceedings of the 12th IEEE International Conference on Network Protocols (ICNP)
Source 1: http://www.cl.cam.ac.uk/users/rja14/Papers/key-infection.pdf
Abstract or Summary:
Future distributed systems may include large self-organizing networks of locally communicating sensor nodes, any small number of which may be subverted by an adversary. Providing security for these sensor networks is important, but the problem is complicated by the fact that managing cryptographic key material is hard: low-cost nodes are neither tamper-proof nor capable of performing public key cryptography efficiently.
In this paper, we show how the key distribution problem can be dealt with in environments with a partially present, passive adversary: a node wishing to communicate securely with other nodes simply generates a symmetric key and sends it in the clear to its neighbours. Despite the apparent insecurity of this primitive, we can use mechanisms for key updating, multipath secrecy amplification and multihop key propagation to build up extremely resilient trust networks where at most a fixed proportion of communications links can be eavesdropped. We discuss applications in which this assumption is sensible.
Many systems must perforce cope with principals who are authenticated weakly, if at all; the resulting issues have often been left in the ‘too hard’ tray. One particular interest of sensor networks is that they present a sufficiently compact and tractable version of this problem. We can perform quantitative analyses and simulations of alternative strategies, some of which we present here. We also hope that this papermay start to challenge the common belief that authentication is substantially about bootstrapping trust. We argue that, in distributed systems where the opponent can subvert any small proportion of nodes, it is more economic to invest in resilience than in bootstrapping.
Do you have additional information to contribute regarding this research paper? If so, please email email@example.com with the details.