170 likes | 388 Views
The Eternity Service. Threat model Service characteristic Design highlights Overall Service structure Protocols used Servers Implementation. http://www.mail.kolej.mff.cuni.cz/~eternity/index.html. Threat model. Blunt influences - natural disasters, vandals, thieves
E N D
The Eternity Service • Threat model • Service characteristic • Design highlights • Overall Service structure • Protocols used • Servers • Implementation http://www.mail.kolej.mff.cuni.cz/~eternity/index.html
Threat model • Blunt influences - natural disasters, vandals, thieves • Amateur opponent - moderate to good knowledge, restricted resources • Professional opponent - excellent knowledge, high motivation, skilled stuff, sufficient resources • Authorities - law enforcement, global influence
Service characteristics • Services: store data for agreed period, retrieve specified information • World-wide system • High reliability and availability • Anonymity • Fully distributed design • No autentization, no privacy
Unlimited availability High resistance Extendibility Fully distributed design Portability and reusability In service upgrade Terseness and simplicity Separation of cryptography Good habits Design goals
Flat structure High ES protection Auxiliary servers Passive behaviour Randomness, concealing Two-layered implementation Freedom principle Design guidelines
Server types - Eternity Server • Each ES represents an entry point • Provides data storage capacity • Assures information retrieval • Automatically discards expired data • Time synchronization • Communication with banks
Server types - Mix server • Padding traffic generation • Supports erm message transfer • Represents simple and cheap way to grow the system size
Server types - AC server • Assures first contact with Service • Collects certificates of servers • Provides ES access certificates and Mix certificates to all subjects
Server types - EPX server • Simple easy to use interface for amateur users without the need of a top quality protection • Additional functions - secret splitting, privacy enhancement, • Local cache for quicker access to frequently requested data
Platform: Posix FreeBSD Unix RSAref + Blowfish gcc Current state: ES with sw-based TCB MX, ACS Client module (alpha versions) Implementation