| P. Verssimo and N. F. Neves, eds., First Specification of APIs and Protocols for the MAFTIA Middleware. Deliverable D24, Project MAFTIA IST- |
....the previous MAFTIA deliverable on the subject [5] they form the basis for realizing generic trusted services with the state machine replication method. Detailed descriptions of the relevant parts of the MAFTIA middleware for asynchronous group communication are specified in D26 [5] and in D24 [22]. Because the updated protocol and API specifications as used here are not available as a MAFTIA deliverable at the time of this writing, we refer to the technical report [8] that documents the parts to be used in the context of secure service replication. 1 2 System Model We briefly recall the ....
....System Model We briefly recall the system model for our distributed trusted service from [5] Our approach is based on protocols for secure state machine replication and coordination among a group of servers connected by a wide area network, such as the Internet. These protocols are described in [5, 22]. The trusted service is implemented by a static group of n servers, of which up to t may fail. They are connected by reliable asynchronous point to point links and have no access to a common clock. Faulty servers can fail in arbitrary, malicious ways and are called corrupted, the remaining ones ....
[Article contains additional citation context not shown here]
P. Verssimo and N. F. Neves, eds., First Specification of APIs and Protocols for the MAFTIA Middleware. Deliverable D24, Project MAFTIA IST-
....across several hosts, and or be accessed securely by users running on remote nodes, even in the presence of malicious faults. The distributed software components of the MAFTIA architecture (middleware and services) are discussed in more detail in MAFTIA deliverables D3 [Alessandri 2001] D23 [Neves Verssimo 2001], D26 [Cachin 2001] D27 [Abghouret al... 2001] In the remainder of this section, we discuss in a little more detail the hardware, the local support, and the middleware. 5.2.3 Hardware We assume that the hardware in individual MAFTIA hosts is untrusted in general. However (see Figure 16) some ....
....TTCB authentication, and trusted random number generation. The latter include services such as the trusted provision of absolute time, duration measurement and timing failure detection. These services and the properties they guarantee are described in more detail in MAFTIA deliverable D24 [Neves Verssimo 2001]. 5.2.5 Middleware The distribution dimension impacts on the protocol design but not on the services provided by each host. These are constructed on the functionality provided by the several middleware modules, represented in Figure 17. These interactions occur through the run time environment. ....
[Article contains additional citation context not shown here]
N. F. Neves and P. Verssimo (Eds.),First Specification of APIs and Protocols for the MAFTIA Middleware, MAFTIA Project, Deliverable D24, 2001.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC