Thu, 18 Nov 1999 16:19:38 -0800
>Credentials, however, are not capabilities. A credential represents a claim
>about a particular entity, and this claim cannot be made to apply to a
>different entity, just as in the college diploma example cited above. Moreover,
>I need to be able to present a credential to others in order for it to be of
>any use to me, and this would make no sense if by the process of presenting a
>credential to someone else they also acquired use of it. Presenting a
>credential thus must be a procedure more like a public-key signature
>verification than like a pointer pass. In presenting a credential I do not
>transfer a power but merely prove some property about me to the entity I am
This sounds to me like proof-carrying code.
Any thoughts as to the costs/benefits/semantics of combining capabilities with proof-carrying code?