asn1: Import ASN.1 modules from RFCs 4043 and 4108

In preparation for adding support for TPM attestations as an authentication
method in bx509d for a host trust bootstrap mechanism based on TPMs and their
endorsement keys and endorsement key certificates.

The plan is to add support to libhx509 and hxtool for PermanentIdentifier
(RFC4043) and HardwareModuleName (RFC4108) SANs, and then to add a query
parameter to bx509d for passing an attestation and a proof-of-possession
(either CMS or CSR), and add an authorizer plugin call for authorizing a device
manufacturer and serial number to hostname.  Support for TPMs w/o endorsement
key certificates should also be possible based on a digest of the endorsement
key as the "serial number".

doc/standardisation/rfc4043.txt

@@ -0,0 +1,843 @@
+
+
+
+
+
+
+Network Working Group                                          D. Pinkas
+Request for Comments: 4043                                          Bull
+Category: Standards Track                                      T. Gindin
+                                                                     IBM
+                                                                May 2005
+
+
+                Internet X.509 Public Key Infrastructure
+                          Permanent Identifier
+
+Status of This Memo
+
+   This document specifies an Internet standards track protocol for the
+   Internet community, and requests discussion and suggestions for
+   improvements.  Please refer to the current edition of the "Internet
+   Official Protocol Standards" (STD 1) for the standardization state
+   and status of this protocol.  Distribution of this memo is unlimited.
+
+Copyright Notice
+
+   Copyright (C) The Internet Society (2005).
+
+Abstract
+
+   This document defines a new form of name, called permanent
+   identifier, that may be included in the subjectAltName extension of a
+   public key certificate issued to an entity.
+
+   The permanent identifier is an optional feature that may be used by a
+   CA to indicate that two or more certificates relate to the same
+   entity, even if they contain different subject name (DNs) or
+   different names in the subjectAltName extension, or if the name or
+   the affiliation of that entity stored in the subject or another name
+   form in the subjectAltName extension has changed.
+
+   The subject name, carried in the subject field, is only unique for
+   each subject entity certified by the one CA as defined by the issuer
+   name field.  However, the new name form can carry a name that is
+   unique for each subject entity certified by a CA.
+
+
+
+
+
+
+
+
+
+
+
+
+Pinkas & Gindin             Standards Track                     [Page 1]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+Table of Contents
+
+   1.  Introduction..................................................  2
+   2.  Definition of a Permanent Identifier..........................  3
+   3.  IANA Considerations...........................................  6
+   4.  Security Considerations.......................................  6
+   5.  References....................................................  7
+       5.1.  Normative References....................................  7
+       5.2.  Informative References..................................  8
+   Appendix A. ASN.1 Syntax..........................................  9
+       A.1.  1988 ASN.1 Module.......................................  9
+       A.2.  1993 ASN.1 Module....................................... 10
+   Appendix B. OID's for organizations............................... 11
+       B.1.  Using IANA (Internet Assigned Numbers Authority)........ 11
+       B.2.  Using an ISO Member Body................................ 12
+       B.3.  Using an ICD (International Code Designator) From
+             British Standards Institution to Specify a New or
+             an Existing Identification Scheme....................... 12
+   Authors' Addresses................................................ 14
+   Full Copyright Statement.......................................... 15
+
+1.  Introduction
+
+   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
+   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
+   document are to be interpreted as described in [RFC2119].
+
+   This specification is based on [RFC3280], which defines underlying
+   certificate formats and semantics needed for a full implementation of
+   this standard.
+
+   The subject field of a public key certificate identifies the entity
+   associated with the public key stored in the subject public key
+   field.  Names and identities of a subject may be carried in the
+   subject field and/or the subjectAltName extension.  Where subject
+   field is non-empty, it MUST contain an X.500 distinguished name (DN).
+   The DN MUST be unique for each subject entity certified by a single
+   CA as defined by the issuer name field.
+
+   The subject name changes whenever any of the components of that name
+   gets changed.  There are several reasons for such a change to happen.
+
+      For employees of a company or organization, the person may get a
+      different position within the same company and thus will move from
+      one organization unit to another one.  Including the organization
+      unit in the name may however be very useful to allow the relying
+      parties (RP's) using that certificate to identify the right
+      individual.
+
+
+
+Pinkas & Gindin             Standards Track                     [Page 2]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+      For citizens, an individual may change their name by legal
+      processes, especially as a result of marriage.
+
+      Any certificate subject identified by geographical location may
+      relocate and change at least some of the location attributes
+      (e.g., country name, state or province, locality, or street).
+
+   A permanent identifier consists of an identifier value assigned
+   within a given naming space by the organization which is
+   authoritative for that naming space.  The organization assigning the
+   identifier value may be the CA that has issued the certificate or a
+   different organization called an Assigner Authority.
+
+   An Assigner Authority may be a government, a government agency, a
+   corporation, or any other sort of organization.  It MUST have a
+   unique identifier to distinguish it from any other such authority.
+   In this standard, that identifier MUST be an object identifier.
+
+   A permanent identifier may be useful in three contexts: access
+   control, non-repudiation and audit records.
+
+      For access control, the permanent identifier may be used in an ACL
+      (Access Control List) instead of the DN or any other form of name
+      and would not need to be changed, even if the subject name of the
+      entity changes.  For non-repudiation, the permanent identifier may
+      be used to link different transactions to the same entity, even
+      when the subject name of the entity changes.
+
+      For audit records, the permanent identifier may be used to link
+      different audit records to the same entity, even when the subject
+      name of the entity changes.
+
+   For two certificates which have been both verified to be valid
+   according to a given validation policy and which contain a permanent
+   identifier, those certificates relate to the same entity if their
+   permanent identifiers match, whatever the content of the DN or other
+   subjectAltName components may be.
+
+   Since the use of permanent identifiers may conflict with privacy, CAs
+   SHOULD advertise to purchasers of certificates the use of permanent
+   identifiers in certificates.
+
+2.  Definition of a Permanent Identifier
+
+   This Permanent Identifier is a name defined as a form of otherName
+   from the GeneralName structure in SubjectAltName, as defined in
+   [X.509] and [RFC3280].
+
+
+
+
+Pinkas & Gindin             Standards Track                     [Page 3]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+   A CA which includes a permanent identifier in a certificate is
+   certifying that any public key certificate containing the same values
+   for that identifier refers to the same entity.
+
+   The use of a permanent identifier is OPTIONAL.  The permanent
+   identifier is defined as follows:
+
+      id-on-permanentIdentifier   OBJECT IDENTIFIER ::= { id-on 3 }
+        PermanentIdentifier ::=     SEQUENCE {
+           identifierValue    UTF8String             OPTIONAL,
+                           -- if absent, use a serialNumber attribute,
+                           -- if there is such an attribute present
+                           -- in the subject DN
+           assigner           OBJECT IDENTIFIER      OPTIONAL
+                           -- if absent, the assigner is
+                           -- the certificate issuer
+   }
+
+   The identifierValue field is optional.
+
+      When the identifierValue field is present, then the
+      identifierValue supports one syntax: UTF8String.
+
+      When the identifierValue field is absent, then the value of the
+      serialNumber attribute (as defined in section 5.2.9 of [X.520])
+      from the deepest RDN of the subject DN is the value to be taken
+      for the identifierValue.  In such a case, there MUST be at least
+      one serialNumber attribute in the subject DN, otherwise the
+      PermanentIdentifier SHALL NOT be used.
+
+   The assigner field is optional.
+
+      When the assigner field is present, then it is an OID which
+      identifies a naming space, i.e., both an Assigner Authority and
+      the type of that field.  Characteristically, the prefix of the OID
+      identifies the Assigner Authority, and a suffix is used to
+      identify the type of permanent identifier.
+
+      When the assigner field is absent, then the permanent identifier
+      is locally unique to the CA.
+
+   The various combinations are detailed below:
+
+   1. Both the assigner and the identifierValue fields are present:
+
+      The identifierValue is the value for that type of identifier.  The
+      assigner field identifies the Assigner Authority and the type of
+      permanent identifier being identified.
+
+
+
+Pinkas & Gindin             Standards Track                     [Page 4]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+      The permanent identifier is globally unique among all CAs.  In
+      such a case, two permanent identifiers of this type match if and
+      only if their assigner fields match and the contents of the
+      identifierValue field in the two permanent identifiers consist of
+      the same Unicode code points presented in the same order.
+
+   2. The assigner field is absent and the identifierValue field is
+      present:
+
+      The Assigner Authority is the CA that has issued the certificate.
+      The identifierValue is given by the CA and the permanent
+      identifier is only local to the CA that has issued the
+      certificate.
+
+      In such a case, two permanent identifiers of this type match if
+      and only if the issuer DN's in the certificates which contain them
+      match using the distinguishedNameMatch rule, as defined in X.501,
+      and the two values of the identifierValue field consist of the
+      same Unicode code points presented in the same order.
+
+   3. Both the assigner and the identifierValue fields are absent:
+
+      If there are one or more RDNs containing a serialNumber attribute
+      (alone or accompanied by other attributes), then the value
+      contained in the serialNumber of the deepest such RDN SHALL be
+      used as the identifierValue; otherwise, the Permanent Identifier
+      definition is invalid and the Permanent Identifier SHALL NOT be
+      used.
+
+      The permanent identifier is only local to the CA that has issued
+      the certificate.  In such a case, two permanent identifiers of
+      this type match if and only if the issuer DN's in the certificates
+      which contain them match and the serialNumber attributes within
+      the subject DN's of those same certificates also match using the
+      caseIgnoreMatch rule.
+
+   4. The assigner field is present and the identifierValue field is
+      absent:
+
+      If there are one or more RDNs containing a serialNumber attribute
+      (alone or accompanied by other attributes), then the value
+      contained in the serialNumber of the deepest such RDN SHALL be
+      used as the identifierValue; otherwise, the Permanent Identifier
+      definition is invalid and the Permanent Identifier SHALL NOT be
+      used.
+
+      The assigner field identifies the Assigner Authority and the type
+      of permanent identifier being identified.
+
+
+
+Pinkas & Gindin             Standards Track                     [Page 5]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+      The permanent identifier is globally unique among all CAs.  In
+      such a case, two permanent identifiers of this type match if and
+      only if their assigner fields match and the contents of the
+      serialNumber attributes within the subject DN's of those same
+      certificates match using the caseIgnoreMatch rule.
+
+   Note: The full arc of the object identifier used to identify the
+         permanent identifier name form is derived using:
+
+      id-pkix OBJECT IDENTIFIER ::= { iso(1) identified-organization(3)
+         dod(6) internet(1) security(5) mechanisms(5) pkix(7) }
+
+      id-on OBJECT IDENTIFIER ::= { id-pkix 8 }   -- other name forms
+
+3.  IANA Considerations
+
+   No IANA actions are necessary.  However, a Private Enterprise Number
+   may be used to construct an OID for the assigner field (see Annex
+   B.1.).
+
+4.  Security Considerations
+
+   A given entity may have at an instant of time or at different
+   instants of time multiple forms of identities.  If the permanent
+   identifier is locally unique to the CA (i.e., the assigner field is
+   not present), then two certificates from the same CA can be compared.
+
+   When two certificates contain identical permanent identifiers, then a
+   relying party may determine that they refer to the same entity.
+
+   If the permanent identifier is globally unique among all CAs (i.e.,
+   the assigner field is present), then two certificates from different
+   CAs can be compared.  When they contain two identical permanent
+   identifiers, then a relying party may determine that they refer to
+   the same entity.  It is the responsibility of the CA to verify that
+   the permanent identifier being included in the certificate refers to
+   the subject being certified.
+
+   The permanent identifier identifies the entity, irrespective of any
+   attribute extension.  When a public key certificate contains
+   attribute extensions, the permanent identifier, if present, should
+   not be used for access control purposes but only for audit purposes.
+   The reason is that since these attributes may change, access could be
+   granted on attributes that were originally present in a certificate
+   issued to that entity but are no longer present in the current
+   certificate.
+
+
+
+
+
+Pinkas & Gindin             Standards Track                     [Page 6]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+   Subject names in certificates are chosen by the issuing CA and are
+   mandated to be unique for each CA; so there can be no name collision
+   between subject names from the same CA.  Such a name may be an end-
+   entity name when the certificate is a leaf certificate, or a CA name,
+   when it is a CA certificate.
+
+   Since a name is only unique towards its superior CA, unless some
+   naming constraints are being used, a name would only be guaranteed to
+   be globally unique when considered to include a sequence of all the
+   names of the superior CAs.  Thus, two certificates that are issued
+   under the same issuer DN and which contain the same permanent
+   identifier extension without an assigner field do not necessarily
+   refer to the same entity.
+
+   Additional checks need to be done, e.g., to check if the public key
+   values of the two CAs which have issued the certificates to be
+   compared are identical or if the sequence of CA names in the
+   certification path from the trust anchor to the CA are identical.
+
+   When the above checks fail, the permanent identifiers may still match
+   if there has been a CA key rollover.  In such a case the checking is
+   more complicated.
+
+   The certification of different CAs with the same DN by different CAs
+   has other negative consequences in various parts of the PKI, notably
+   rendering the IssuerAndSerialNumber structure in [RFC3852] section
+   10.2.4 ambiguous.
+
+   The permanent identifier allows organizations to create links between
+   different certificates associated with an entity issued with or
+   without overlapping validity periods.  This ability to link different
+   certificates may conflict with privacy.  It is therefore important
+   that a CA clearly disclose any plans to issue certificates which
+   include a permanent identifier to potential subjects of those
+   certificates.
+
+5.  References
+
+5.1.  Normative References
+
+   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
+              Requirement Levels", BCP 14, RFC 2119, March 1997.
+
+   [RFC3280]  Housley, R., Polk, W., Ford, W., and D. Solo, "Internet
+              X.509 Public Key Infrastructure Certificate and
+              Certificate Revocation List (CRL) Profile", RFC 3280,
+              April 2002.
+
+
+
+
+Pinkas & Gindin             Standards Track                     [Page 7]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+   [UTF-8]    Yergeau, F., "UTF-8, a transformation format of ISO
+              10646", STD 63, RFC 3629, November 2003.
+
+   [X.501]    ITU-T Rec X.501 | ISO 9594-2: 2001: Information technology
+              - Open Systems Interconnection - The Directory: Models,
+              February 2001.
+
+5.2.  Informative References
+
+   [RFC3852]  Housley, R., "Cryptographic Message Syntax (CMS)", RFC
+              3852, July 2004.
+
+   [X.509]    ITU-T Recommendation X.509 (1997 E): Information
+              Technology - Open Systems Interconnection - The Directory:
+              Authentication Framework, June 1997.
+
+   [X.520]    ITU-T Recommendation X.520: Information Technology - Open
+              Systems Interconnection - The Directory: Selected
+              Attribute Types, June 1997.
+
+   [X.660]    ITU-T Recommendation X.660: Information Technology - Open
+              Systems Interconnection - Procedures for the Operation of
+              OSI Registration Authorities: General Procedures, 1992.
+
+   [X.680]    ITU-T Recommendation X.680: Information Technology -
+              Abstract Syntax Notation One, 1997.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Pinkas & Gindin             Standards Track                     [Page 8]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+Appendix A.  ASN.1 Syntax
+
+   As in RFC 2459, ASN.1 modules are supplied in two different variants
+   of the ASN.1 syntax.
+
+   This section describes data objects used by conforming PKI components
+   in an "ASN.1-like" syntax.  This syntax is a hybrid of the 1988 and
+   1993 ASN.1 syntaxes.  The 1988 ASN.1 syntax is augmented with 1993
+   the UNIVERSAL Type UTF8String.
+
+   The ASN.1 syntax does not permit the inclusion of type statements in
+   the ASN.1 module, and the 1993 ASN.1 standard does not permit use of
+   the new UNIVERSAL types in modules using the 1988 syntax.  As a
+   result, this module does not conform to either version of the ASN.1
+   standard.
+
+   Appendix A.1 may be parsed by an 1988 ASN.1-parser by replacing the
+   definitions for the UNIVERSAL Types with the 1988 catch-all "ANY".
+
+   Appendix A.2 may be parsed "as is" by an 1997-compliant ASN.1 parser.
+
+   In case of discrepancies between these modules, the 1988 module is
+   the normative one.
+
+Appendix A.1.  1988 ASN.1 Module
+
+  PKIXpermanentidentifier88 {iso(1) identified-organization(3) dod(6)
+         internet(1) security(5) mechanisms(5) pkix(7) id-mod(0)
+         id-mod-perm-id-88(28) }
+
+  DEFINITIONS EXPLICIT TAGS ::=
+
+     BEGIN
+
+     -- EXPORTS ALL --
+
+     IMPORTS
+
+  -- UTF8String, / move hyphens before slash if UTF8String does not
+  -- resolve with your compiler
+  -- The content of this type conforms to [UTF-8].
+
+          id-pkix
+                FROM PKIX1Explicit88 { iso(1) identified-organization(3)
+                dod(6) internet(1) security(5) mechanisms(5) pkix(7)
+                id-mod(0) id-pkix1-explicit(18) } ;
+                -- from [RFC3280]
+
+
+
+
+Pinkas & Gindin             Standards Track                     [Page 9]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+     -- Permanent identifier Object Identifier and Syntax
+
+     id-on   OBJECT IDENTIFIER ::= { id-pkix 8 }
+
+     id-on-permanentIdentifier   OBJECT IDENTIFIER ::= { id-on 3 }
+
+     PermanentIdentifier ::= SEQUENCE {
+          identifierValue    UTF8String             OPTIONAL,
+                          -- if absent, use the serialNumber attribute
+                          -- if there is a single such attribute present
+                          -- in the subject DN
+          assigner           OBJECT IDENTIFIER      OPTIONAL
+                          -- if absent, the assigner is
+                          -- the certificate issuer
+  }
+
+  END
+
+Appendix A.2.  1993 ASN.1 Module
+
+PKIXpermanentidentifier93 {iso(1) identified-organization(3) dod(6)
+       internet(1) security(5) mechanisms(5) pkix(7) id-mod(0)
+       id-mod-perm-id-93(29) }
+
+   DEFINITIONS EXPLICIT TAGS ::=
+
+   BEGIN
+
+   -- EXPORTS ALL --
+
+   IMPORTS
+
+        id-pkix
+              FROM PKIX1Explicit88 { iso(1) identified-organization(3)
+              dod(6) internet(1) security(5) mechanisms(5) pkix(7)
+              id-mod(0) id-pkix1-explicit(18) }
+               -- from [RFC3280]
+
+        ATTRIBUTE
+              FROM InformationFramework {joint-iso-itu-t ds(5) module(1)
+              informationFramework(1) 4};
+               -- from [X.501]
+
+   -- Permanent identifier Object Identifiers
+
+   id-on   OBJECT IDENTIFIER ::= { id-pkix 8 }
+
+   id-on-permanentIdentifier   OBJECT IDENTIFIER ::= { id-on 3 }
+
+
+
+Pinkas & Gindin             Standards Track                    [Page 10]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+   -- Permanent Identifier
+
+   permanentIdentifier ATTRIBUTE ::= {
+          WITH SYNTAX     PermanentIdentifier
+          ID              id-on-permanentIdentifier }
+
+   PermanentIdentifier ::= SEQUENCE {
+        identifierValue    UTF8String             OPTIONAL,
+                        -- if absent, use the serialNumber attribute
+                        -- if there is a single such attribute present
+                        -- in the subject DN
+        assigner           OBJECT IDENTIFIER      OPTIONAL
+                        -- if absent, the assigner is
+                        -- the certificate issuer
+}
+
+END
+
+Appendix B.  OID's for Organizations
+
+   In order to construct an OID for the assigner field, organizations
+   need first to have a registered OID for themselves.  Such an OID must
+   be obtained from a registration authority following [X.660].  In some
+   cases, OID's are provided for free.  In other cases a one-time fee is
+   required.  The main difference lies in the nature of the information
+   that is collected at the time of registration and how this
+   information is verified for its accuracy.
+
+Appendix B.1.  Using IANA (Internet Assigned Numbers Authority)
+
+   The application form for a Private Enterprise Number in the IANA's
+   OID list is: http://www.iana.org/cgi-bin/enterprise.pl.
+
+   Currently, IANA assigns numbers for free.  The IANA-registered
+   Private Enterprises prefix is:
+   iso.org.dod.internet.private.enterprise (1.3.6.1.4.1)
+
+   These numbers are used, among other things, for defining private SNMP
+   MIBs.
+
+   The official assignments under this OID are stored in the IANA file
+   "enterprise-numbers" available at:
+   http://www.iana.org/assignments/enterprise-numbers
+
+
+
+
+
+
+
+
+Pinkas & Gindin             Standards Track                    [Page 11]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+Appendix B.2.  Using an ISO Member Body
+
+   ISO has defined the OID structure in a such a way so that every ISO
+   member-body has its own unique OID.  Then every ISO member-body is
+   free to allocate its own arc space below.
+
+   Organizations and enterprises may contact the ISO member-body where
+   their organization or enterprise is established to obtain an
+   organization/enterprise OID.
+
+   Currently, ISO members do not assign organization/enterprise OID's
+   for free.
+
+   Most of them do not publish registries of such OID's which they have
+   assigned, sometimes restricting the access to registered
+   organizations or preferring to charge inquirers for the assignee of
+   an OID on a per-inquiry basis.  The use of OID's from an ISO member
+   organization which does not publish such a registry may impose extra
+   costs on the CA that needs to make sure that the OID corresponds to
+   the registered organization.
+
+   As an example, AFNOR (Association Francaise de Normalisation - the
+   French organization that is a member of ISO) has defined an arc to
+   allocate OID's for companies:
+
+   {iso (1) member-body (2) fr (250) type-org (1) organisation (n)}
+
+Appendix B.3.  Using an ICD (International Code Designator) From British
+               Standards Institution to Specify a New or an Existing
+               Identification Scheme
+
+   The International Code Designator (ICD) is used to uniquely identify
+   an ISO 6523 compliant organization identification scheme.  ISO 6523
+   is a standard that defines the proper structure of an identifier and
+   the registration procedure for an ICD.  The conjunction of the ICD
+   with an identifier issued by the registration authority is worldwide
+   unique.
+
+   The basic structure of the code contains the following components:
+
+   -  the ICD value: The International Code Designator issued to the
+      identification scheme makes the identifier worldwide unique (up to
+      4 digits),
+
+   -  the Organization, usually a company or governmental body (up to 35
+      characters),
+
+
+
+
+
+Pinkas & Gindin             Standards Track                    [Page 12]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+   -  an Organization Part (OPI - Organization Part Identifier).  An
+      identifier allocated to a particular Organization Part (optional,
+      up to 35 characters)
+
+   The ICD is also equivalent to an object identifier (OID) under the
+   arc {1(iso).  3(identified organization)}.
+
+   On behalf of ISO, British Standards Institution (BSI) is the
+   Registration Authority for organizations under the arc {iso (1)
+   org(3)}.  This means BSI registers code issuing authorities
+   (organizations) by ICD values which are equivalent to OIDs of the
+   form {iso (1) org(3) icd(xxxx)}.  The corresponding IdentifierValue
+   is the code value of the scheme identified by icd(xxxx).
+
+   As an example, the ICD 0012 was allocated to European Computer
+   Manufacturers Association: ECMA.  Thus the OID for ECMA is {iso(1)
+   org(3) ecma(12)}.
+
+   For registration with BSI, a "Sponsoring Authority" has to vouch for
+   the Applying organization.  Registration is not free.  Recognized
+   "Sponsoring Authorities" are: ISO Technical Committees or
+   (Sub)Committees, Member Bodies of ISO or International Organizations
+   having a liaison status with ISO or with any of its Technical
+   (Sub)Committees.
+
+   An example of a Sponsoring Authority is the EDIRA Association (EDI/EC
+   Registration Authority, web: http://www.edira.org,
+   email:info@edira.org).
+
+   The numerical list of all ICDs that have been issued is posted on its
+   webpage: http://www.edira.org/documents.htm#icd-List
+
+   Note: IANA owns ICD code 0090, but (presumably) it isn't intending to
+   use it for the present purpose.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Pinkas & Gindin             Standards Track                    [Page 13]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+Authors' Addresses
+
+   Denis Pinkas
+   Bull
+   Rue Jean-Jaures BP 68
+   78340 Les Clayes-sous-Bois
+   FRANCE
+
+   EMail: Denis.Pinkas@bull.net
+
+
+   Thomas Gindin
+   IBM Corporation
+   6710 Rockledge Drive
+   Bethesda, MD 20817
+   USA
+
+   EMail: tgindin@us.ibm.com
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+Pinkas & Gindin             Standards Track                    [Page 14]
+
+RFC 4043                  Permanent Identifier                  May 2005
+
+
+Full Copyright Statement
+
+   Copyright (C) The Internet Society (2005).
+
+   This document is subject to the rights, licenses and restrictions
+   contained in BCP 78, and except as set forth therein, the authors
+   retain all their rights.
+
+   This document and the information contained herein are provided on an
+   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
+   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
+   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
+   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
+   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
+   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
+
+Intellectual Property
+
+   The IETF takes no position regarding the validity or scope of any
+   Intellectual Property Rights or other rights that might be claimed to
+   pertain to the implementation or use of the technology described in
+   this document or the extent to which any license under such rights
+   might or might not be available; nor does it represent that it has
+   made any independent effort to identify any such rights.  Information
+   on the procedures with respect to rights in RFC documents can be
+   found in BCP 78 and BCP 79.
+
+   Copies of IPR disclosures made to the IETF Secretariat and any
+   assurances of licenses to be made available, or the result of an
+   attempt made to obtain a general license or permission for the use of
+   such proprietary rights by implementers or users of this
+   specification can be obtained from the IETF on-line IPR repository at
+   http://www.ietf.org/ipr.
+
+   The IETF invites any interested party to bring to its attention any
+   copyrights, patents or patent applications, or other proprietary
+   rights that may cover technology that may be required to implement
+   this standard.  Please address the information to the IETF at ietf-
+   ipr@ietf.org.
+
+Acknowledgement
+
+   Funding for the RFC Editor function is currently provided by the
+   Internet Society.
+
+
+
+
+
+
+
+Pinkas & Gindin             Standards Track                    [Page 15]
+

lib/asn1/Makefile.am

@@ -23,6 +23,8 @@ libasn1_la_LIBADD = \
 
 BUILT_SOURCES =				\
 	$(gen_files_rfc2459:.x=.c)	\
+	$(gen_files_rfc4043:.x=.c)	\
+	$(gen_files_rfc4108:.x=.c)	\
 	$(gen_files_cms:.x=.c)		\
 	$(gen_files_krb5:.x=.c)		\
 	$(gen_files_ocsp:.x=.c)	\
@@ -38,6 +40,8 @@ gen_files_krb5 = asn1_krb5_asn1.x
 gen_files_cms = asn1_cms_asn1.x
 gen_files_crmf = asn1_crmf_asn1.x
 gen_files_rfc2459 = asn1_rfc2459_asn1.x
+gen_files_rfc4043 = asn1_rfc4043_asn1.x
+gen_files_rfc4108 = asn1_rfc4108_asn1.x
 gen_files_ocsp = asn1_ocsp_asn1.x
 gen_files_pkinit = asn1_pkinit_asn1.x
 gen_files_pkcs10 = asn1_pkcs10_asn1.x
@@ -48,6 +52,8 @@ gen_files_test_template = test_template_asn1-template.x
 gen_files_test = asn1_test_asn1.x
 gen_files_digest = asn1_digest_asn1.x
 gen_files_kx509 = asn1_kx509_asn1.x
+gen_files_rfc4043 = asn1_rfc4043_asn1.x
+gen_files_rfc4108 = asn1_rfc4108_asn1.x
 
 oid_resolution.lo: $(BUILT_SOURCES)
 
@@ -139,6 +145,8 @@ check_ber_LDADD = $(check_gen_LDADD)
 CLEANFILES = \
 	$(BUILT_SOURCES) \
 	$(gen_files_rfc2459) \
+	$(gen_files_rfc4043) \
+	$(gen_files_rfc4108) \
 	$(gen_files_cms) \
 	$(gen_files_krb5) \
 	$(gen_files_ocsp) \
@@ -154,6 +162,8 @@ CLEANFILES = \
 	$(nodist_check_gen_SOURCES) \
 	asn1_err.c asn1_err.h \
 	rfc2459_asn1_files rfc2459_asn1*.h* \
+	rfc4043_asn1_files rfc4043_asn1*.h* \
+	rfc4108_asn1_files rfc4108_asn1*.h* \
 	cms_asn1_files cms_asn1*.h* \
 	crmf_asn1_files crmf_asn1*.h* \
 	krb5_asn1_files krb5_asn1*.h* \
@@ -179,6 +189,8 @@ nodist_include_HEADERS += pkinit_asn1.h
 nodist_include_HEADERS += cms_asn1.h
 nodist_include_HEADERS += crmf_asn1.h
 nodist_include_HEADERS += rfc2459_asn1.h
+nodist_include_HEADERS += rfc4043_asn1.h
+nodist_include_HEADERS += rfc4108_asn1.h
 nodist_include_HEADERS += ocsp_asn1.h
 nodist_include_HEADERS += pkcs8_asn1.h
 nodist_include_HEADERS += pkcs9_asn1.h
@@ -192,6 +204,8 @@ priv_headers += pkinit_asn1-priv.h
 priv_headers += cms_asn1-priv.h
 priv_headers += crmf_asn1-priv.h
 priv_headers += rfc2459_asn1-priv.h
+priv_headers += rfc4043_asn1-priv.h
+priv_headers += rfc4108_asn1-priv.h
 priv_headers += ocsp_asn1-priv.h
 priv_headers += pkcs8_asn1-priv.h
 priv_headers += pkcs9_asn1-priv.h
@@ -223,6 +237,8 @@ $(gen_files_pkcs12) pkcs12_asn1.hx pkcs12_asn1-priv.hx: pkcs12_asn1_files
 $(gen_files_digest) digest_asn1.hx digest_asn1-priv.hx: digest_asn1_files
 $(gen_files_kx509) kx509_asn1.hx kx509_asn1-priv.hx: kx509_asn1_files
 $(gen_files_rfc2459) rfc2459_asn1.hx rfc2459_asn1-priv.hx: rfc2459_asn1_files
+$(gen_files_rfc4043) rfc4043_asn1.hx rfc4043_asn1-priv.hx: rfc4043_asn1_files
+$(gen_files_rfc4108) rfc4108_asn1.hx rfc4108_asn1-priv.hx: rfc4108_asn1_files
 $(gen_files_cms) cms_asn1.hx cms_asn1-priv.hx: cms_asn1_files
 $(gen_files_crmf) crmf_asn1.hx crmf_asn1-priv.hx: crmf_asn1_files
 $(gen_files_test) test_asn1.hx test_asn1-priv.hx: test_asn1_files
@@ -231,6 +247,12 @@ $(gen_files_test_template) test_template_asn1.hx test_template_asn1-priv.hx: tes
 rfc2459_asn1_files: asn1_compile$(EXEEXT) $(srcdir)/rfc2459.asn1
 	$(ASN1_COMPILE) --one-code-file --option-file=$(srcdir)/rfc2459.opt $(srcdir)/rfc2459.asn1 rfc2459_asn1 || (rm -f rfc2459_asn1_files ; exit 1)
 
+rfc4043_asn1_files: asn1_compile$(EXEEXT) $(srcdir)/rfc4043.asn1
+	$(ASN1_COMPILE) --one-code-file $(srcdir)/rfc4043.asn1 rfc4043_asn1 || (rm -f rfc4043_asn1_files ; exit 1)
+
+rfc4108_asn1_files: asn1_compile$(EXEEXT) $(srcdir)/rfc4108.asn1
+	$(ASN1_COMPILE) --one-code-file $(srcdir)/rfc4108.asn1 rfc4108_asn1 || (rm -f rfc4108_asn1_files ; exit 1)
+
 cms_asn1_files: asn1_compile$(EXEEXT) $(srcdir)/cms.asn1 $(srcdir)/cms.opt
 	$(ASN1_COMPILE) --one-code-file --option-file=$(srcdir)/cms.opt $(srcdir)/cms.asn1 cms_asn1 || (rm -f cms_asn1_files ; exit 1)
 
@@ -293,6 +315,8 @@ EXTRA_DIST =		\
 	pkcs10.asn1	\
 	pkinit.asn1	\
 	rfc2459.asn1	\
+	rfc4043.asn1	\
+	rfc4108.asn1	\
 	setchgpw2.asn1	\
 	test.asn1	\
 	test.gen	\

lib/asn1/NTMakefile

@@ -43,6 +43,10 @@ gen_files_crmf		= $(OBJ)\asn1_crmf_asn1.x
 
 gen_files_rfc2459	= $(OBJ)\asn1_rfc2459_asn1.x
 
+gen_files_rfc4043	= $(OBJ)\asn1_rfc4043_asn1.x
+
+gen_files_rfc4108	= $(OBJ)\asn1_rfc4108_asn1.x
+
 gen_files_ocsp		= $(OBJ)\asn1_ocsp_asn1.x
 
 gen_files_pkinit	= $(OBJ)\asn1_pkinit_asn1.x
@@ -117,6 +121,8 @@ LIBASN1_OBJS=	\
 	$(OBJ)\extra.obj		\
 	$(OBJ)\timegm.obj		\
 	$(gen_files_rfc2459:.x=.obj)	\
+	$(gen_files_rfc4043:.x=.obj)	\
+	$(gen_files_rfc4108:.x=.obj)	\
 	$(gen_files_cms:.x=.obj)	\
 	$(gen_files_crmf:.x=.obj)	\
 	$(gen_files_krb5:.x=.obj)		\
@@ -175,6 +181,10 @@ $(gen_files_kx509:.x=.c)    : $$(@R).x
 
 $(gen_files_rfc2459:.x=.c)  : $$(@R).x
 
+$(gen_files_rfc4043:.x=.c)  : $$(@R).x
+
+$(gen_files_rfc4108:.x=.c)  : $$(@R).x
+
 $(gen_files_cms:.x=.c)	    : $$(@R).x
 
 $(gen_files_crmf:.x=.c)	    : $$(@R).x
@@ -255,6 +265,22 @@ $(gen_files_rfc2459) $(OBJ)\rfc2459_asn1.hx: $(BINDIR)\asn1_compile.exe rfc2459.
 	|| ($(RM) $(OBJ)\rfc2459_asn1.h ; exit /b 1)
 	cd $(SRCDIR)
 
+$(gen_files_rfc4043) $(OBJ)\rfc4043_asn1.hx: $(BINDIR)\asn1_compile.exe rfc4043.asn1
+	cd $(OBJ)
+	$(BINDIR)\asn1_compile.exe \
+		--one-code-file \
+		$(SRCDIR)\rfc4043.asn1 rfc4043_asn1 \
+	|| ($(RM) $(OBJ)\rfc4043_asn1.h ; exit /b 1)
+	cd $(SRCDIR)
+
+$(gen_files_rfc4108) $(OBJ)\rfc4108_asn1.hx: $(BINDIR)\asn1_compile.exe rfc4108.asn1
+	cd $(OBJ)
+	$(BINDIR)\asn1_compile.exe \
+		--one-code-file \
+		$(SRCDIR)\rfc4108.asn1 rfc4108_asn1 \
+	|| ($(RM) $(OBJ)\rfc4108_asn1.h ; exit /b 1)
+	cd $(SRCDIR)
+
 $(gen_files_cms) $(OBJ)\cms_asn1.hx: $(BINDIR)\asn1_compile.exe cms.asn1 cms.opt
 	cd $(OBJ)
 	$(BINDIR)\asn1_compile.exe \
@@ -304,12 +330,16 @@ GENINCFILES=			    \
 	$(INCDIR)\pkcs10_asn1.h	    \
 	$(INCDIR)\pkinit_asn1.h	    \
 	$(INCDIR)\rfc2459_asn1.h    \
+	$(INCDIR)\rfc4043_asn1.h    \
+	$(INCDIR)\rfc4108_asn1.h    \
 	$(OBJ)\krb5_asn1-priv.h	    \
 	$(OBJ)\ocsp_asn1-priv.h     \
 	$(OBJ)\pkinit_asn1-priv.h   \
 	$(OBJ)\cms_asn1-priv.h	    \
 	$(OBJ)\crmf_asn1-priv.h	    \
 	$(OBJ)\rfc2459_asn1-priv.h  \
+	$(OBJ)\rfc4043_asn1-priv.h  \
+	$(OBJ)\rfc4108_asn1-priv.h  \
 	$(OBJ)\pkcs8_asn1-priv.h    \
 	$(OBJ)\pkcs9_asn1-priv.h    \
 	$(OBJ)\pkcs10_asn1-priv.h   \

lib/asn1/libasn1-exports.def

@@ -19,6 +19,14 @@ EXPORTS
 	asn1_KDCFastFlags_units
 	asn1_KDCOptions_units
 	asn1_KeyUsage_units
+	asn1_oid_id_aa_communityIdentifiers	DATA
+	asn1_oid_id_aa_decryptKeyID	DATA
+	asn1_oid_id_aa_firmwarePackageID	DATA
+	asn1_oid_id_aa_firmwarePackageInfo	DATA
+	asn1_oid_id_aa_implCompressAlgs	DATA
+	asn1_oid_id_aa_implCryptoAlgs	DATA
+	asn1_oid_id_aa_targetHardwareIDs	DATA
+	asn1_oid_id_aa_wrappedFirmwareKey	DATA
 	asn1_oid_id_aes_128_cbc	DATA
 	asn1_oid_id_aes_192_cbc	DATA
 	asn1_oid_id_aes_256_cbc	DATA
@@ -40,6 +48,9 @@ EXPORTS
 	asn1_oid_id_at_streetAddress	DATA
 	asn1_oid_id_at_surname	DATA
 	asn1_oid_id_at_title	DATA
+	asn1_oid_id_ct_firmwareLoadError	DATA
+	asn1_oid_id_ct_firmwareLoadReceipt	DATA
+	asn1_oid_id_ct_firmwarePackage	DATA
 	asn1_oid_id_dhpublicnumber	DATA
 	asn1_oid_id_domainComponent	DATA
 	asn1_oid_id_dsa	DATA
@@ -73,6 +84,9 @@ EXPORTS
 	asn1_oid_id_nist_aes_algs	DATA
 	asn1_oid_id_nistAlgorithm	DATA
 	asn1_oid_id_nist_sha_algs	DATA
+	asn1_oid_id_on	DATA
+	asn1_oid_id_on_hardwareModuleName	DATA
+	asn1_oid_id_on_permanentIdentifier	DATA
 	asn1_oid_id_pbeWithSHAAnd128BitRC2_CBC	DATA
 	asn1_oid_id_pbeWithSHAAnd128BitRC4	DATA
 	asn1_oid_id_pbeWithSHAAnd2_KeyTripleDES_CBC	DATA
@@ -274,12 +288,16 @@ EXPORTS
 	copy_CMSIdentifier
 	copy_CMSRC2CBCParameter
 	copy_CMSVersion
+	copy_CommunityIdentifier
+	copy_CommunityIdentifiers
 	copy_ContentEncryptionAlgorithmIdentifier
 	copy_ContentInfo
 	copy_ContentType
 	copy_CRLCertificateList
 	copy_CRLDistributionPoints
 	copy_CRLReason
+	copy_CurrentFWConfig
+	copy_DecryptKeyIdentifier
 	copy_DHNonce
 	copy_DHParameter
 	copy_DHPublicKey
@@ -334,14 +352,27 @@ EXPORTS
 	copy_ExternalPrincipalIdentifiers
 	copy_ExtKeyUsage
 	copy_FastOptions
+	copy_FirmwarePackageIdentifier
+	copy_FirmwarePackageInfo
+	copy_FirmwarePackageLoadError
+	copy_FirmwarePackageLoadErrorCode
+	copy_FirmwarePackageLoadReceipt
+	copy_FirmwarePkgData
+	copy_FWErrorVersion
+	copy_FWReceiptVersion
 	copy_GeneralName
 	copy_GeneralNames
 	copy_GeneralSubtree
 	copy_GeneralSubtrees
+	copy_HardwareModuleName
+	copy_HardwareModules
+	copy_HardwareSerialEntry
 	copy_heim_any
 	copy_heim_any_set
 	copy_HostAddress
 	copy_HostAddresses
+	copy_ImplementedCompressAlgorithms
+	copy_ImplementedCryptoAlgorithms
 	copy_IssuerAndSerialNumber
 	copy_KDCDHKeyInfo
 	copy_KDCDHKeyInfo_Win2k
@@ -442,6 +473,7 @@ EXPORTS
 	copy_PA_ServerReferralData
 	copy_PA_SERVER_REFERRAL_DATA
 	copy_PA_SvrReferralData
+	copy_PermanentIdentifier
 	copy_PKAuthenticator
 	copy_PKAuthenticator_Win2k
 	copy_PKCS12_Attribute
@@ -465,6 +497,9 @@ EXPORTS
 	copy_PkinitSP80056AOtherInfo
 	copy_PkinitSuppPubInfo
 	copy_PKIXXmppAddr
+	copy_PreferredOrLegacyPackageIdentifier
+	copy_PreferredOrLegacyStalePackageIdentifier
+	copy_PreferredPackageIdentifier
 	copy_Principal
 	copy_PrincipalName
 	copy_Principals
@@ -491,6 +526,7 @@ EXPORTS
 	copy_SubjectInfoAccessSyntax
 	copy_SubjectKeyIdentifier
 	copy_SubjectPublicKeyInfo
+	copy_TargetHardwareIdentifiers
 	copy_TBSCertificate
 	copy_TBSCRLCertList
 	copy_TD_DH_PARAMETERS
@@ -510,7 +546,9 @@ EXPORTS
 	copy_UnprotectedAttributes
 	copy_ValidationParms
 	copy_Validity
+	copy_VendorLoadErrorCode
 	copy_Version
+	copy_WrappedFirmwareKey
 	decode_AccessDescription
 	decode_AD_AND_OR
 	decode_AD_IF_RELEVANT
@@ -556,12 +594,16 @@ EXPORTS
 	decode_CMSIdentifier
 	decode_CMSRC2CBCParameter
 	decode_CMSVersion
+	decode_CommunityIdentifier
+	decode_CommunityIdentifiers
 	decode_ContentEncryptionAlgorithmIdentifier
 	decode_ContentInfo
 	decode_ContentType
 	decode_CRLCertificateList
 	decode_CRLDistributionPoints
 	decode_CRLReason
+	decode_CurrentFWConfig
+	decode_DecryptKeyIdentifier
 	decode_DHNonce
 	decode_DHParameter
 	decode_DHPublicKey
@@ -616,14 +658,27 @@ EXPORTS
 	decode_ExternalPrincipalIdentifiers
 	decode_ExtKeyUsage
 	decode_FastOptions
+	decode_FirmwarePackageIdentifier
+	decode_FirmwarePackageInfo
+	decode_FirmwarePackageLoadError
+	decode_FirmwarePackageLoadErrorCode
+	decode_FirmwarePackageLoadReceipt
+	decode_FirmwarePkgData
+	decode_FWErrorVersion
+	decode_FWReceiptVersion
 	decode_GeneralName
 	decode_GeneralNames
 	decode_GeneralSubtree
 	decode_GeneralSubtrees
+	decode_HardwareModuleName
+	decode_HardwareModules
+	decode_HardwareSerialEntry
 	decode_heim_any
 	decode_heim_any_set
 	decode_HostAddress
 	decode_HostAddresses
+	decode_ImplementedCompressAlgorithms
+	decode_ImplementedCryptoAlgorithms
 	decode_IssuerAndSerialNumber
 	decode_KDCDHKeyInfo
 	decode_KDCDHKeyInfo_Win2k
@@ -724,6 +779,7 @@ EXPORTS
 	decode_PA_ServerReferralData
 	decode_PA_SERVER_REFERRAL_DATA
 	decode_PA_SvrReferralData
+	decode_PermanentIdentifier
 	decode_PKAuthenticator
 	decode_PKAuthenticator_Win2k
 	decode_PKCS12_Attribute
@@ -747,6 +803,9 @@ EXPORTS
 	decode_PkinitSP80056AOtherInfo
 	decode_PkinitSuppPubInfo
 	decode_PKIXXmppAddr
+	decode_PreferredOrLegacyPackageIdentifier
+	decode_PreferredOrLegacyStalePackageIdentifier
+	decode_PreferredPackageIdentifier
 	decode_Principal
 	decode_PrincipalName
 	decode_Principals
@@ -773,6 +832,7 @@ EXPORTS
 	decode_SubjectInfoAccessSyntax
 	decode_SubjectKeyIdentifier
 	decode_SubjectPublicKeyInfo
+	decode_TargetHardwareIdentifiers
 	decode_TBSCertificate
 	decode_TBSCRLCertList
 	decode_TD_DH_PARAMETERS
@@ -792,7 +852,9 @@ EXPORTS
 	decode_UnprotectedAttributes
 	decode_ValidationParms
 	decode_Validity
+	decode_VendorLoadErrorCode
 	decode_Version
+	decode_WrappedFirmwareKey
 	der_copy_bit_string
 	der_copy_bmp_string
 	der_copy_generalized_time
@@ -965,12 +1027,16 @@ EXPORTS
 	encode_CMSIdentifier
 	encode_CMSRC2CBCParameter
 	encode_CMSVersion
+	encode_CommunityIdentifier
+	encode_CommunityIdentifiers
 	encode_ContentEncryptionAlgorithmIdentifier
 	encode_ContentInfo
 	encode_ContentType
 	encode_CRLCertificateList
 	encode_CRLDistributionPoints
 	encode_CRLReason
+	encode_CurrentFWConfig
+	encode_DecryptKeyIdentifier
 	encode_DHNonce
 	encode_DHParameter
 	encode_DHPublicKey
@@ -1025,14 +1091,27 @@ EXPORTS
 	encode_ExternalPrincipalIdentifiers
 	encode_ExtKeyUsage
 	encode_FastOptions
+	encode_FirmwarePackageIdentifier
+	encode_FirmwarePackageInfo
+	encode_FirmwarePackageLoadError
+	encode_FirmwarePackageLoadErrorCode
+	encode_FirmwarePackageLoadReceipt
+	encode_FirmwarePkgData
+	encode_FWErrorVersion
+	encode_FWReceiptVersion
 	encode_GeneralName
 	encode_GeneralNames
 	encode_GeneralSubtree
 	encode_GeneralSubtrees
+	encode_HardwareModuleName
+	encode_HardwareModules
+	encode_HardwareSerialEntry
 	encode_heim_any
 	encode_heim_any_set
 	encode_HostAddress
 	encode_HostAddresses
+	encode_ImplementedCompressAlgorithms
+	encode_ImplementedCryptoAlgorithms
 	encode_IssuerAndSerialNumber
 	encode_KDCDHKeyInfo
 	encode_KDCDHKeyInfo_Win2k
@@ -1133,6 +1212,7 @@ EXPORTS
 	encode_PA_ServerReferralData
 	encode_PA_SERVER_REFERRAL_DATA
 	encode_PA_SvrReferralData
+	encode_PermanentIdentifier
 	encode_PKAuthenticator
 	encode_PKAuthenticator_Win2k
 	encode_PKCS12_Attribute
@@ -1156,6 +1236,9 @@ EXPORTS
 	encode_PkinitSP80056AOtherInfo
 	encode_PkinitSuppPubInfo
 	encode_PKIXXmppAddr
+	encode_PreferredOrLegacyPackageIdentifier
+	encode_PreferredOrLegacyStalePackageIdentifier
+	encode_PreferredPackageIdentifier
 	encode_Principal
 	encode_PrincipalName
 	encode_Principals
@@ -1182,6 +1265,7 @@ EXPORTS
 	encode_SubjectInfoAccessSyntax
 	encode_SubjectKeyIdentifier
 	encode_SubjectPublicKeyInfo
+	encode_TargetHardwareIdentifiers
 	encode_TBSCertificate
 	encode_TBSCRLCertList
 	encode_TD_DH_PARAMETERS
@@ -1201,7 +1285,9 @@ EXPORTS
 	encode_UnprotectedAttributes
 	encode_ValidationParms
 	encode_Validity
+	encode_VendorLoadErrorCode
 	encode_Version
+	encode_WrappedFirmwareKey
 	FastOptions2int
 	free_AccessDescription
 	free_AD_AND_OR
@@ -1248,12 +1334,16 @@ EXPORTS
 	free_CMSIdentifier
 	free_CMSRC2CBCParameter
 	free_CMSVersion
+	free_CommunityIdentifier
+	free_CommunityIdentifiers
 	free_ContentEncryptionAlgorithmIdentifier
 	free_ContentInfo
 	free_ContentType
 	free_CRLCertificateList
 	free_CRLDistributionPoints
 	free_CRLReason
+	free_CurrentFWConfig
+	free_DecryptKeyIdentifier
 	free_DHNonce
 	free_DHParameter
 	free_DHPublicKey
@@ -1308,14 +1398,27 @@ EXPORTS
 	free_ExternalPrincipalIdentifiers
 	free_ExtKeyUsage
 	free_FastOptions
+	free_FirmwarePackageIdentifier
+	free_FirmwarePackageInfo
+	free_FirmwarePackageLoadError
+	free_FirmwarePackageLoadErrorCode
+	free_FirmwarePackageLoadReceipt
+	free_FirmwarePkgData
+	free_FWErrorVersion
+	free_FWReceiptVersion
 	free_GeneralName
 	free_GeneralNames
 	free_GeneralSubtree
 	free_GeneralSubtrees
+	free_HardwareModuleName
+	free_HardwareModules
+	free_HardwareSerialEntry
 	free_heim_any
 	free_heim_any_set
 	free_HostAddress
 	free_HostAddresses
+	free_ImplementedCompressAlgorithms
+	free_ImplementedCryptoAlgorithms
 	free_IssuerAndSerialNumber
 	free_KDCDHKeyInfo
 	free_KDCDHKeyInfo_Win2k
@@ -1416,6 +1519,7 @@ EXPORTS
 	free_PA_ServerReferralData
 	free_PA_SERVER_REFERRAL_DATA
 	free_PA_SvrReferralData
+	free_PermanentIdentifier
 	free_PKAuthenticator
 	free_PKAuthenticator_Win2k
 	free_PKCS12_Attribute
@@ -1439,6 +1543,9 @@ EXPORTS
 	free_PkinitSP80056AOtherInfo
 	free_PkinitSuppPubInfo
 	free_PKIXXmppAddr
+	free_PreferredOrLegacyPackageIdentifier
+	free_PreferredOrLegacyStalePackageIdentifier
+	free_PreferredPackageIdentifier
 	free_Principal
 	free_PrincipalName
 	free_Principals
@@ -1465,6 +1572,7 @@ EXPORTS
 	free_SubjectInfoAccessSyntax
 	free_SubjectKeyIdentifier
 	free_SubjectPublicKeyInfo
+	free_TargetHardwareIdentifiers
 	free_TBSCertificate
 	free_TBSCRLCertList
 	free_TD_DH_PARAMETERS
@@ -1484,7 +1592,9 @@ EXPORTS
 	free_UnprotectedAttributes
 	free_ValidationParms
 	free_Validity
+	free_VendorLoadErrorCode
 	free_Version
+	free_WrappedFirmwareKey
 	heim_any_cmp
 	_heim_der_set_sort
 	_heim_fix_dce
@@ -1552,12 +1662,16 @@ EXPORTS
 	length_CMSIdentifier
 	length_CMSRC2CBCParameter
 	length_CMSVersion
+	length_CommunityIdentifier
+	length_CommunityIdentifiers
 	length_ContentEncryptionAlgorithmIdentifier
 	length_ContentInfo
 	length_ContentType
 	length_CRLCertificateList
 	length_CRLDistributionPoints
 	length_CRLReason
+	length_CurrentFWConfig
+	length_DecryptKeyIdentifier
 	length_DHNonce
 	length_DHParameter
 	length_DHPublicKey
@@ -1612,14 +1726,27 @@ EXPORTS
 	length_ExternalPrincipalIdentifiers
 	length_ExtKeyUsage
 	length_FastOptions
+	length_FirmwarePackageIdentifier
+	length_FirmwarePackageInfo
+	length_FirmwarePackageLoadError
+	length_FirmwarePackageLoadErrorCode
+	length_FirmwarePackageLoadReceipt
+	length_FirmwarePkgData
+	length_FWErrorVersion
+	length_FWReceiptVersion
 	length_GeneralName
 	length_GeneralNames
 	length_GeneralSubtree
 	length_GeneralSubtrees
+	length_HardwareModuleName
+	length_HardwareModules
+	length_HardwareSerialEntry
 	length_heim_any
 	length_heim_any_set
 	length_HostAddress
 	length_HostAddresses
+	length_ImplementedCompressAlgorithms
+	length_ImplementedCryptoAlgorithms
 	length_IssuerAndSerialNumber
 	length_KDCDHKeyInfo
 	length_KDCDHKeyInfo_Win2k
@@ -1720,6 +1847,7 @@ EXPORTS
 	length_PA_ServerReferralData
 	length_PA_SERVER_REFERRAL_DATA
 	length_PA_SvrReferralData
+	length_PermanentIdentifier
 	length_PKAuthenticator
 	length_PKAuthenticator_Win2k
 	length_PKCS12_Attribute
@@ -1743,6 +1871,9 @@ EXPORTS
 	length_PkinitSP80056AOtherInfo
 	length_PkinitSuppPubInfo
 	length_PKIXXmppAddr
+	length_PreferredOrLegacyPackageIdentifier
+	length_PreferredOrLegacyStalePackageIdentifier
+	length_PreferredPackageIdentifier
 	length_Principal
 	length_PrincipalName
 	length_Principals
@@ -1769,6 +1900,7 @@ EXPORTS
 	length_SubjectInfoAccessSyntax
 	length_SubjectKeyIdentifier
 	length_SubjectPublicKeyInfo
+	length_TargetHardwareIdentifiers
 	length_TBSCertificate
 	length_TBSCRLCertList
 	length_TD_DH_PARAMETERS
@@ -1788,7 +1920,9 @@ EXPORTS
 	length_UnprotectedAttributes
 	length_ValidationParms
 	length_Validity
+	length_VendorLoadErrorCode
 	length_Version
+	length_WrappedFirmwareKey
 	remove_AttributeValues
 	remove_AuthorizationData
 	remove_Certificates

lib/asn1/rfc4043.asn1

@@ -0,0 +1,30 @@
+PKIXpermanentidentifier88 {iso(1) identified-organization(3) dod(6)
+       internet(1) security(5) mechanisms(5) pkix(7) id-mod(0)
+       id-mod-perm-id-88(28) }
+
+DEFINITIONS EXPLICIT TAGS ::=
+
+   BEGIN
+
+   -- EXPORTS ALL --
+   -- IMPORTS id-pkix FROM rfc2459; but asn1_compile doesn't handle this
+
+
+   -- Permanent identifier Object Identifier and Syntax
+
+   id-on   OBJECT IDENTIFIER ::= { iso(1) identified-organization(3)
+               dod(6) internet(1) security(5) mechanisms(5) pkix(7) 8 }
+
+   id-on-permanentIdentifier   OBJECT IDENTIFIER ::= { id-on 3 }
+
+   PermanentIdentifier ::= SEQUENCE {
+        identifierValue    UTF8String             OPTIONAL,
+                        -- if absent, use the serialNumber attribute
+                        -- if there is a single such attribute present
+                        -- in the subject DN
+        assigner           OBJECT IDENTIFIER      OPTIONAL
+                        -- if absent, the assigner is
+                        -- the certificate issuer
+}
+
+END

lib/asn1/rfc4108.asn1

@@ -0,0 +1,202 @@
+CMSFirmwareWrapper
+    { iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1)
+      pkcs-9(9) smime(16) modules(0) cms-firmware-wrap(22) }
+
+DEFINITIONS IMPLICIT TAGS ::= BEGIN
+
+IMPORTS
+    EnvelopedData
+    FROM cms -- [CMS]
+         { iso(1) member-body(2) us(840) rsadsi(113549)
+           pkcs(1) pkcs-9(9) smime(16) modules(0) cms-2004(24) };
+
+
+-- Firmware Package Content Type and Object Identifier
+
+id-ct-firmwarePackage OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) ct(1) 16 }
+
+FirmwarePkgData ::= OCTET STRING
+
+
+-- Firmware Package Signed Attributes and Object Identifiers
+
+id-aa-firmwarePackageID OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) aa(2) 35 }
+
+PreferredPackageIdentifier ::= SEQUENCE {
+  fwPkgID OBJECT IDENTIFIER,
+  verNum INTEGER (0..MAX) }
+
+PreferredOrLegacyPackageIdentifier ::= CHOICE {
+  preferred PreferredPackageIdentifier,
+  legacy OCTET STRING }
+
+PreferredOrLegacyStalePackageIdentifier ::= CHOICE {
+  preferredStaleVerNum INTEGER (0..MAX),
+  legacyStaleVersion OCTET STRING }
+
+FirmwarePackageIdentifier ::= SEQUENCE {
+  name PreferredOrLegacyPackageIdentifier,
+  stale PreferredOrLegacyStalePackageIdentifier OPTIONAL }
+
+
+id-aa-targetHardwareIDs OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) aa(2) 36 }
+
+TargetHardwareIdentifiers ::= SEQUENCE OF OBJECT IDENTIFIER
+
+
+id-aa-decryptKeyID OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) aa(2) 37 }
+
+DecryptKeyIdentifier ::= OCTET STRING
+
+
+id-aa-implCryptoAlgs OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) aa(2) 38 }
+
+ImplementedCryptoAlgorithms ::= SEQUENCE OF OBJECT IDENTIFIER
+
+id-aa-implCompressAlgs OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) aa(2) 43 }
+
+ImplementedCompressAlgorithms ::= SEQUENCE OF OBJECT IDENTIFIER
+
+
+id-aa-communityIdentifiers OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) aa(2) 40 }
+
+HardwareSerialEntry ::= CHOICE {
+  all NULL,
+  single OCTET STRING,
+  block SEQUENCE {
+    low OCTET STRING,
+    high OCTET STRING } }
+
+HardwareModules ::= SEQUENCE {
+  hwType OBJECT IDENTIFIER,
+  hwSerialEntries SEQUENCE OF HardwareSerialEntry }
+
+CommunityIdentifier ::= CHOICE {
+  communityOID OBJECT IDENTIFIER,
+  hwModuleList HardwareModules }
+
+CommunityIdentifiers ::= SEQUENCE OF CommunityIdentifier
+
+id-aa-firmwarePackageInfo OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) aa(2) 42 }
+
+FirmwarePackageInfo ::= SEQUENCE {
+  fwPkgType INTEGER OPTIONAL,
+  dependencies SEQUENCE OF
+    PreferredOrLegacyPackageIdentifier OPTIONAL }
+
+
+-- Firmware Package Unsigned Attributes and Object Identifiers
+
+id-aa-wrappedFirmwareKey OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) aa(2) 39 }
+
+WrappedFirmwareKey ::= EnvelopedData
+
+
+-- Firmware Package Load Receipt Content Type and Object Identifier
+
+id-ct-firmwareLoadReceipt OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) ct(1) 17 }
+
+FWReceiptVersion ::= INTEGER { v1(1) }
+
+FirmwarePackageLoadReceipt ::= SEQUENCE {
+  version FWReceiptVersion DEFAULT 1, -- v1, but asn1_compile doesn't handle this
+  hwType OBJECT IDENTIFIER,
+  hwSerialNum OCTET STRING,
+  fwPkgName PreferredOrLegacyPackageIdentifier,
+  trustAnchorKeyID OCTET STRING OPTIONAL,
+  decryptKeyID [1] OCTET STRING OPTIONAL }
+
+-- Firmware Package Load Error Report Content Type
+-- and Object Identifier
+
+id-ct-firmwareLoadError OBJECT IDENTIFIER ::= {
+  iso(1) member-body(2) us(840) rsadsi(113549) pkcs(1) pkcs9(9)
+  smime(16) ct(1) 18 }
+
+FWErrorVersion ::= FWReceiptVersion
+
+FirmwarePackageLoadErrorCode ::= ENUMERATED {
+  decodeFailure                (1),
+  badContentInfo               (2),
+  badSignedData                (3),
+  badEncapContent              (4),
+  badCertificate               (5),
+  badSignerInfo                (6),
+  badSignedAttrs               (7),
+  badUnsignedAttrs             (8),
+  missingContent               (9),
+  noTrustAnchor               (10),
+  notAuthorized               (11),
+  badDigestAlgorithm          (12),
+  badSignatureAlgorithm       (13),
+  unsupportedKeySize          (14),
+  signatureFailure            (15),
+  contentTypeMismatch         (16),
+  badEncryptedData            (17),
+  unprotectedAttrsPresent     (18),
+  badEncryptContent           (19),
+  badEncryptAlgorithm         (20),
+  missingCiphertext           (21),
+  noDecryptKey                (22),
+  decryptFailure              (23),
+  badCompressAlgorithm        (24),
+  missingCompressedContent    (25),
+  decompressFailure           (26),
+  wrongHardware               (27),
+  stalePackage                (28),
+  notInCommunity              (29),
+  unsupportedPackageType      (30),
+  missingDependency           (31),
+  wrongDependencyVersion      (32),
+  insufficientMemory          (33),
+  badFirmware                 (34),
+  unsupportedParameters       (35),
+  breaksDependency            (36),
+  otherError                  (99) }
+
+VendorLoadErrorCode ::= INTEGER
+
+CurrentFWConfig ::= SEQUENCE {
+  fwPkgType INTEGER OPTIONAL,
+  fwPkgName PreferredOrLegacyPackageIdentifier }
+
+FirmwarePackageLoadError ::= SEQUENCE {
+  version FWErrorVersion DEFAULT 1, -- v1, but see above
+  hwType OBJECT IDENTIFIER,
+  hwSerialNum OCTET STRING,
+  errorCode FirmwarePackageLoadErrorCode,
+  vendorErrorCode VendorLoadErrorCode OPTIONAL,
+  fwPkgName PreferredOrLegacyPackageIdentifier OPTIONAL,
+  config [1] SEQUENCE OF CurrentFWConfig OPTIONAL }
+
+-- Other Name syntax for Hardware Module Name
+
+id-on-hardwareModuleName OBJECT IDENTIFIER ::= {
+  iso(1) identified-organization(3) dod(6) internet(1) security(5)
+  mechanisms(5) pkix(7) on(8) 4 }
+
+HardwareModuleName ::= SEQUENCE {
+  hwType OBJECT IDENTIFIER,
+  hwSerialNum OCTET STRING }
+
+END