1. Donkey Project Introduction and ideas around February 21, 2003 Yuri Demchenko

2. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _2 Outlines  Problems in traditional PKI and Identity Management  Donkey goals  Donkey Functionality  Design issues  Timetable  Next steps  Discussion: u Where the Donkey can be of use for RIPE NCC

3. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _3 Problems in PKI and Identity Management X.509 PKI is a heavy-weight solution and usually enterprise oriented:  Requires Certificate Authority (CA) to create and trust a certificate (PKC)  Certificate creation/revocation mechanism is complex, slow and expensive  LDAP as a standard mechanism to publish X.509 Certs is not easily extensible and (generically) not globally scaled Distributed applications and mobile users require secure remote access to electronic credentials and identity information P2P networks normally (based on DHT) require non-hierarchical (non-PKI) security infrastructure Advent of XML/SOAP based standards for SSO/Identity management creates technological alternative for traditional PKI and PMI

4. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _4 Donkey and DNSSEC DNSSEC can be a source of public keys for zones/nodes but it's not intended to provide this service for other applications:  Intended for host names, not arbitrary names  Updates are slow (propagation through caches, administrative overhead)  Requires DNSSEC protocol for public key access/request (standard request for KEY and SIG RRs) Donkey can provide (shadow/alternative) key distribution infrastructure using application specific protocols to off-load DNSSEC

5. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _5 Donkey Goal(s) Open extendable system for public key and Identity management Initial stage Open global distributed system for publishing and retrieving named, signed public keys Intended development Identity management for federated cross-domain AuthN and AuthZ Donkey website: http://www.nlnetlabs.nl/donkey/

6. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _6 What is Donkey: Donkey functionality  Donkey allows anyone to publish a named key, together with optional data (Donkey package) u Multiple parties are allowed to publish a key with the same name. Applications must select the correct key when multiple keys match u Donkey is NOT a permanent storage: key must be republished to remain available u Donkey does NOT define a policy for key/payload usage –This is an application specific function  Donkey allows anyone to query for a published key, based on the key's name (required) and signers (optional)  Donkey allows anyone to sign a published key

7. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _7 Design issues: Package structure (Proprietary) Internal format (Python data object) but XML based exchange format  Package ID  Content u Header –Flags –Names u Owner Public Key – must be unique u Body –Payload Application dependent content and format Intended for AA and Identity management May include specific format definition (e.g., embedded XML Schema)  Signatures

8. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _8 Design considerations Build upon existing solutions and standards  But still capable to do a low start Gradual development  Build up upon key storage/management engine XML for package extensibility and exchange  Including prospective use of the XML Protocol

9. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _9 Existing OpenSource solutions for AA and PMI Donkey will be built upon existing PKI and AA applications: PGP Key Server Internet2 PubCookie/WebISO and Shibboleth/AA PAPI (AuthZ and Web SSO) A-Select (AuthZ and Web SSO) PERMIS (PrivilEge and Role Management Infrastructure Standards Validation Project) Akenti (cross-domain AA for Grid applications)

10. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _10 Standards for security assertions PGP X.509 Public Key Certificate (PKC) X.509 Attribute Certificate (AC) for Privilege Management SAML (Security Assertion Mark-up Language) Liberty Alliance Network Identity (XML and SAML based) Web Services Security (SOAP Extensions)

11. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _11 PKC vs AC: Purposes  X.509 PKC binds an identity and a public key  AC is a component of X.509 Role-based PMI u AC contains no public key u AC may contain attributes that specify group membership, role, security clearance, or other authorisation information associated with the AC holder u Analogy: PKC is like passport, and AC is like entry visa  PKC is used for Authentication and AC is used for Authorisation –AC may be included into Authentication message  PKC relies on Certification Authority and AC requires Attribute Authority (AA)

12. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _12 X.509 PKC Fields and Extensions – check with RFC 3280 X.509 PKC Fields  Serial Number  Subject  Subject Public Key  Issuer Unique ID  Subject Unique ID X.509 PKC Extensions  Standard Extensions u Authority Key Identifier u Subject Key Identifier u Key Usage u Extended Key Usage u CRL Distribution List u Private Key Usage Period u Certificate Policies u Policy Mappings u Subject Alternative Name u Issuer Alternative Name u Subject Directory Attributes u Basic Constraints u Name Constraints X.509 PKC Fields  Private Extensions u Authority Information Access u Subject Information Access  Custom Extensions

13. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _13 X.509 PKC Extensions format Identifier: Key Usage: - 2.5.29.15 Critical: yes Key Usage: Digital Signature Key CertSign Crl Sign

14. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _14 AC vs PKC: Certificates structure X.509 PKC  Version  Serial number  Signature  Issuer  Validity  Subject  Subject Public key info  Issuer unique identifier  Extensions AC  Version  Holder  Issuer  Signature  Serial number  Validity  Attributes  Issuer unique ID  Extensions

15. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _15 AC Attribute Types and AC Extensions AC Attribute Types  Service Authentication Informaion  Access Identity  Charging Identity  Group  Role  Clearance  Profile of AC AC Extensions  Audit Identity u To protect privacy and provide anonymity u May be traceable via AC issuer  AC Targeting  Authority Key Identifier  Authority Information Access  CRL Distribution Points

16. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _16 Donkey Project milestones  Overview and inventory/planning - current stage u Selected basic technologies and development environment u Overview document  March-April: Prospective applications area overview u Requirements (common and specific for applications) u Draft Package and Protocol description/definition  April-May: API(s) definition and Donkey prototyping u API requirements  June-August: Development and pilot implementation for 1-2 applications

17. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _17 Donkey current status Just started work on Donkey prototype  Key generation (DSA or RSA keys)  Creating a new Donkey package  Add and verify signature to/of an existing Donkey package  Data model and XML DTD/Schema for Donkey packages Goal: Create a base for experiments with application specific payloads

18. ©February 21, 2003. Amsterdam. Donkey Project Slide2 _18 Some specific next tasks  Overview of existing solutions for AA and Identity management  Analysis of applications specific requirements  Scalability analysis  Trust analysis  Threats analysis