…on and encoding of public key materials and digital signatures are defined in [ RFC3279 ], [ RFC4055 ], and [ RFC4491 ]. Implementations of this specification are not required to use any particular cryptographic algorithms. However, conforming implementations that use the algorit…
…on and encoding of public key materials and digital signatures are defined in [ RFC3279 ], [ RFC4055 ], and [ RFC4491 ]. Implementations of this specification are not required to use any particular cryptographic algorithms. However, conforming implementations that use the algorit…
…on and encoding of public key materials and digital signatures are defined in [ RFC3279 ], [ RFC4055 ], and RFC4491 ]. Implementations of this specification are not required to use any particular cryptographic algorithms. However, conforming implementations that use the algorithm…
…on and encoding of public key materials and digital signatures are defined in [ RFC3279 ], [ RFC4055 ], and RFC4491 ]. Implementations of this specification are not required to use any particular cryptographic algorithms. However, conforming implementations that use the algorithm…
…tribute. For named curves that are identified by OIDs, such as those defined in RFC3279 ] and [ RFC4055 ], the OID SHOULD be encoded according to [ URN-OID ]. Conformant applications MUST support the dsig11:NamedCurve element and the 256-bit prime field curve as identified by the…
…ibute. For named curves that are identified by OIDs, such as those defined in [ RFC3279 ] and [ RFC4055 ], the OID SHOULD be encoded according to [ URN-OID ]. Conformant applications MUST support the dsig11:NamedCurve element and the 256-bit prime field curve as identified by the…
rfc3279 This is a purely informative rendering of an RFC that includes verified errata. This rendering may not be used as a reference. The following 'Verified' errata have been incorporated in this document: EID 2048 EID 307 EID 4036 EID 4102 EID 7296 Network Working Group W. Pol…
… the "Digital Signature Standard" [ FIPS186-3 ]. This document updates RFC 3279 RFC3279 ] Sections 2.1 2.2.2 , and 2.2.3. Note that RFC 5480 RFC5480 ] updates Sections 2.3.5 (ASN.1 Module), and 5 (Security Considerations) of RFC 3279 Dang, et al. Standards Track [Page 2] RFC 5758…
…2 Note Registration requires a standards-track RFC which updates or obsoletes [ RFC3279 ]. Available Formats CSV Hash Function Name OID Reference "md2" 1.2.840.113549.2.2 RFC3279 "md5" 1.2.840.113549.2.5 RFC3279 "sha-1" 1.3.14.3.2.26 RFC3279 "sha-224" 2.16.840.1.101.3.4.2.4 RFC40…
… the "Digital Signature Standard" [ FIPS186-3 ]. This document updates RFC 3279 RFC3279 ] Sections 2.1 2.2.2 , and 2.2.3. Note that RFC 5480 RFC5480 ] updates Sections 2.3.5 (ASN.1 Module), and 5 (Security Considerations) of RFC 3279 Dang, et al. Standards Track [Page 2] RFC 5758…
… the "Digital Signature Standard" [ FIPS186-3 ]. This document updates RFC 3279 RFC3279 ] Sections 2.1 2.2.2 , and 2.2.3. Note that RFC 5480 RFC5480 ] updates Sections 2.3.5 (ASN.1 Module), and 5 (Security Considerations) of RFC 3279 Dang, et al. Standards Track [Page 2] RFC 5758…
…Use of MD2 has been specified in the following RFCs: Proposed Standard (PS): o [RFC3279] Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile. o [RFC4572] Connection-Oriented Media Transport over the…
…sing RSA with SHA-1 (identified by the sha1WithRSAEncryption OID specified in [ RFC3279 ]) and the Digital Signature Algorithm (DSA) with SHA-1 (identified by the id-dsa-with-sha1 OID specified in [ RFC3279 ]). Clients MAY support other algorithms. 4.4 . Extensions This section d…
…using RSA with SHA-1 (identified by the sha1WithRSAEncryption OID specified in [RFC3279]) and the Digital Signature Algorithm (DSA) with SHA-1 (identified by the id-dsa-with-sha1 OID specified in [RFC3279]). Clients MAY support other algorithms. 4.4. Extensions This section defin…
…using RSA with SHA-1 (identified by the sha1WithRSAEncryption OID specified in [RFC3279]) and the Digital Signature Algorithm (DSA) with SHA-1 (identified by the id-dsa-with-sha1 OID specified in [RFC3279]). Clients MAY support other algorithms. 4.4. Extensions This section defin…