| CCITT. Recommendation X.509: The directory-authentication framework, 1989. Blue book - Melbourne, Geneve. |
....[2] 13] which provides the security functionality of the Globus Toolkit. For authentication, GSI uses X.509 proxy certificates [22] to provide credentials for users and to allow for delegation and single sign on. Proxy certificates are similar to the standard X. 509 end entity certificates (EECs) [6] from which they are derived. The primary difference is that users issue proxy certificates to create a short term (e.g. one day) delegation of their rights to another entity (e.g. a process rtmning on their behalf) as opposed to EECs, which are issued by certificate authorities to assign a ....
....of these sites have policy requirements dictated by their funding agencies to identify users of their computational resources. We proposed that the CAS server, which authenticates the user and hence has access to their identity, could encode the user identity in a non critical X. 509 extension [6] to the proxy certificate. This solution was also of concern to the resource providers because it required them to trust the CAS server as to the identity of the user. This caused them to place more trust in the CAS server than they were comfortable with. This concern led to the redesign of CAS ....
[Article contains additional citation context not shown here]
CCITT Recommendation X.509: The Directory - Authentication Framework. 1988.
....have to resort to the distribution of revocation lists, which is much faster, albeit less reliable. In our protocol, a leader may revoke the membership of any members or leaders of the same group. Note that we revoke membership, i.e. hGroupkey; Memberkeyi pairs, and not keys (as in X. 509 or PGP [CCI88,Zim95]) or certificates (as in SPKI) Leaders are not allowed remove members from other groups, so universal revocation of a key cannot be allowed, and it is more convenient to revoke all the redundant certificate chains at once than to revoke each certificate separately. The revocation entries have ....
CCITT. Recommendation X.509, The Directory - Authentication Framework, volume VIII of CCITT Blue Book, pages 48--81. 1988.
....They are delegated from key to key with chains of signed certificates. These certificates form a network of trust relations between the keys. This way, local authorities are free to form trust relations without the need for the kind of global hierarchy of trusted servers as, for example, in X. 509 [4]. The goal of this paper is to present an abstract model for the networks of delegation formed by public key certificates between keys. We formalize the concept of a delegation network and present a formal semantics for the delegation. The model is used for proving the equivalence of several ....
Recommendation X.509, The Directory - Authentication Framework, volume VIII of CCITT Blue Book, pages 48--81. CCITT, 1988.
No context found.
CCITT. Recommendation X.509: The directory-authentication framework, 1989. Blue book - Melbourne, Geneve.
No context found.
CCITT (1998). The directory authentication framework. CCITT Recommendation X.509.
No context found.
CCITT Recommendation X.509, The Directory - Authentication Framework, 1988.
No context found.
CCITT Blue Book Recommendation X.509, The Directory-Authentication Framework, Geneva, March 1988; also ISO 9594-8.
No context found.
CCITT. Recommendation X.509: The Directory -- Authentication Framework, 1988.
No context found.
CCITT. Recommendation X.509: The directory-authentication framework, 1988.
No context found.
CCITT Recommendation X.509 (1988), "The Directory - Authentication Framework".
No context found.
CCITT, Recommendation X.509: The Directory Authentication Framework, December 1988.
No context found.
CCITT. Recommendation X.509: The Directory -- Authentication Framework, 1988.
No context found.
CCITT. Recommendation X.509: "The Directory - Authentication Framework". 1988.
No context found.
CCITT Recommendation X.509 (1988), "The Directory - Authentication Framework".
No context found.
CCITT Recommendation X.509 (1988), "The Directory - Authentication Framework".
No context found.
CCITT. Recommendation X.509: the directory -- authentication framework, 1988.
No context found.
CCITT, Recommendation X.509: The Directory Authentication Framework, December 1988.
No context found.
CCITT. Recommendation X.509: The Directory - Authentication Framework. 1988.
No context found.
CCITT, Recommendation X.509: The Directory Authentication Framework, December 1988.
No context found.
CCITT. Recommendation X.509: the directory -- authentication framework, 1988.
No context found.
CCITT. The Directory Authentication Framework. Recommendation X.509, 1988.
No context found.
CCITT Recommendation X.509, "The Directory - Authentication Framework", November 1988, (Developed in collaboration, and technically aligned, with ISO 9594-8).
No context found.
CCITT Recommendation X.509: The Directory - Authentication Framework. 1988.
No context found.
CCITT, Recommendation X. 509-1989, The directory-authentication framework, Consultation Committee, International Telephone and Telegraph, International Telecommunication Union, Geneva (1989).
No context found.
CCITT Recommendation X.509: The Directory -- Authentication Framework. 1988
First 50 documents Next 50
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