Browsing by Author "Randell, B."
Now showing 1 - 6 of 6
Results Per Page
Sort Options
- Complete Specification of APIs and Protocols for the MAFTIA MiddlewarePublication . Armstrong, J.; Cachin, C.; Correia, Miguel; Costa, A.; Miranda, Hugo; Neves, Nuno Ferreira; Neves, Nuno M.; Poritz, J. A.; Randell, B.; Lung, Lau Cheuk; Rodrigues, Luís; Stroud, Robert J.; Veríssimo, Paulo; Waidner, M.; Welch, I. S.This document describes the complete specification of the APIs and Protocols for the MAFTIA Middleware. The architecture of the middleware subsystem has been described in a previous document, where the several modules and services were introduced: Activity Services; Communication Services; Network Abstraction; Trusted and Untrusted Components. The purpose of the present document is to make concrete the functionality of the middleware components, by defining their application programming interfaces, and describing the protocols implementing the above-mentioned functionality
- Conceptual Model and Architecture of MAFTIAPublication . Adelsbach, A.; Cachin, C.; Creese, S.; Deswarte, Y.; Kursawe, K.; Laprie, J.-C.; Powell, David; Randell, B.; Riodan, J.; Ryan, P.; Simmionds, W.; Stroud, Robert J.; Veríssimo, Paulo; Waidner, M.; Wespi, A.This deliverable builds on the work reported in [MAFTIA 2000] and [Powell and Stroud 2001]. It contains a further refinement of the MAFTIA conceptual model and a revised discussion of the MAFTIA architecture. It also introduces the work done in MAFTIA on verification and assessment of security properties, which is reported on in more detail in [Adelsbach and Creese 2003]
- First Specification of APIs and Protocols for the MAFTIA MiddlewarePublication . Armstrong, J.; Cachin, C.; Correia, Miguel; Costa, A.; Miranda, Hugo; Neves, Nuno Ferreira; Neves, Nuno M.; Poritz, J. A.; Randell, B.; Lung, Lau Cheuk; Rodrigues, Luís; Stroud, Robert J.; Veríssimo, Paulo; Waidner, M.; Welch, I. S.This document describes the first specification of the APIs and Protocols for the MAFTIA Middleware. The architecture of the middleware subsystem has been described in a previous document, where the several modules and services were introduced: Activity Services; Communication Services; Network Abstraction; Trusted and Untrusted Components. The purpose of the present document is to make concrete the functionality of the middleware components, by defining their application programming interfaces, and describing the protocols implementing the above-mentioned functionality
- MAFTIA Conceptual Model and ArchitecturePublication . Adelsbach, A.; Cachin, C.; Creese, S.; Deswarte, Y.; Kursawe, K.; Laprie, J.-C.; Pfitzmann, B.; Powell, David; Randell, B.; Riodan, J.; Stroud, Robert J.; Veríssimo, Paulo; Waidner, M.; Welch, I. S.This document builds on the work reported in MAFTIA deliverable D1. It contains a refinement of the MAFTIA conceptual model and a discussion of the MAFTIA architecture. It also introduces the work done in WP6 on verification and assessment of security properties, which is reported on in more detail in MAFTIA deliverable D4
- MAFTIA: Reference Model and Use CasesPublication . Cachin, C.; Camenisch, J.; Deswarte, Y.; Dobson, J.; Horne, D.; Kursawe, K.; Laprie, J.-C.; Lebraud, J.-C.; Long, D.; McCutcheon, T.; Muller, J.; Petzold, F.; Pfitzmann, B.; Powell, David; Randell, B.; Schunter, M.; Shoup, V.; Veríssimo, Paulo; Trouessin, G.; Stroud, Robert J.; Waidner, M.; Welch, I. S.This document constitutes the first deliverable of MAFTIA work package 1. The objective of this work package is to define a consistent framework for ensuring the dependability of distributed applications in the face of a wide class of threats. In particular, the aim is to develop a coherent set of concepts for an architecture that can tolerate deliberately malicious faults, such as intrusions, in applications distributed over the Internet. The intrusions of concern include not only those perpetrated by external penetrators, but also those carried out by corrupt insiders, i.e., users who are authorized to access the system but not authorized for the accessed data, program or resource, and administrators who misuse their rights. Although intrusions are the primary class of targeted faults, the architecture should also be adequately robust towards accidental physical faults and accidental design faults
- Service and Protocol Architecture for the MAFTIA MiddlewarePublication . Cachin, C.; Correia, Miguel; McCutcheon, T.; Neves, Nuno Ferreira; Pfitzmann, B.; Randell, B.; Schunter, M.; Stroud, Robert J.; Veríssimo, Paulo; Waidner, M.; Welch, I. S.This document describes the specification of the MAFTIA middleware architecture. This specification focusses on the models, building blocks and services. It describes the tradeoffs made in terms of models, the choices of building blocks and their topology, and the portfolio of services to be offered by the MAFTIA middleware to applications and high-level services. In particular, regarding the system model, it presents a detailed discussion on the fault, synchrony, topological, and group models, which were used to guide the overall architecture. The architecture was divided into two main levels, the site part which connects to the network and handles all inter-host operations, and a participant part which takes care of all distributed activities and relies on the services provided by the site-part components