Abstract
A colleague in UCC, John Morrison, has been working on the development of an architecture for mobile code, WebCom1, and in the last year or so we’ve been looking at using trust management systems to control the secure scheduling or dissemination of this mobile code. The main components to the architecture are masters and clients. A master schedules out operations to clients (the scheduling can be done in a push or in a pull fashion) and the clients use KeyNote to determine whether or not a master is authorised to schedule mobile code to a particular client. The code could be a COM object, for example, and the client wants to make sure that it’s coming from a trustworthy source with trustworthy parameters. On the other side the master is also using KeyNote to determine whether clients are authorised to execute. So it’s a very straightforward application of KeyNote.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2002 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Foley, S.N. (2002). Trust Management and Whether to Delegate. In: Christianson, B., Malcolm, J.A., Crispo, B., Roe, M. (eds) Security Protocols. Security Protocols 2001. Lecture Notes in Computer Science, vol 2467. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-45807-7_24
Download citation
DOI: https://doi.org/10.1007/3-540-45807-7_24
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-44263-9
Online ISBN: 978-3-540-45807-4
eBook Packages: Springer Book Archive