…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…

…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…

…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…

…7, < https://www.rfc-editor.org/info/rfc8174 >. 13.2 . Informative References [ RFC3279 ] Bassham, L., Polk, W., and R. Housley, "Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 3279 , DOI…

…tted by using the RSAPublicKey type as specified in Section 2.3.1 of RFC 3279 [ RFC3279 ]. The RSA key length SHOULD be at least 384 bits. Other public key types are undesirable in SEND, as they may result in incompatibilities between implementations. The length of this field is …

…o be used with Elliptic Curve Digital Signature Algorithm (ECDSA) public keys. [RFC3279] and [RFC5280] describe the structure of X.509v3 certificates to be used with RSA and Digital Signature Algorithm (DSA) public keys. [RFC5759] provides additional guidance for ECDSA keys in Su…

…tted by using the RSAPublicKey type as specified in Section 2.3.1 of RFC 3279 [ RFC3279 ]. The RSA key length SHOULD be at least 384 bits. Other public key types are undesirable in SEND, as they may result in incompatibilities between implementations. The length of this field is …

…186-2 ], IEEE 1363 [ IEEE1363 ], IEEE 1363a [ IEEE1363a ], and SEC1 [ SEC1 ]. [ RFC3279 ] describes ways to carry ECDSA keys in X.509 certificates. [ FIPS-186-2 ], [ SEC2 ], and [ X9.62 ] provide recommended elliptic curve domain parameters for use with ECDSA. Blake-Wilson, et al…

… be used with Elliptic Curve Digital Signature Algorithm (ECDSA) public keys. [ RFC3279 ] and [ RFC5280 ] describe the structure of X.509v3 certificates to be used with RSA and Digital Signature Algorithm (DSA) public keys. [ RFC5759 ] provides additional guidance for ECDSA keys …

…4 RFC 8174 , DOI 10.17487/RFC8174, May 2017, < >. 13.2 . Informative References RFC3279 ] Bassham, L., Polk, W., and R. Housley, "Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 3279 , DOI…

…4 RFC 8174 , DOI 10.17487/RFC8174, May 2017, < >. 13.2 . Informative References RFC3279 ] Bassham, L., Polk, W., and R. Housley, "Algorithms and Identifiers for the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile", RFC 3279 , DOI…

…ection 2.2.1 ("RSA Signature Algorithm") of RFC 3279, and defined in RFC 3447. [RFC3279] [RFC3447] Otherwise, the keytype attribute is in the unknown state The given key type is not supported. Return the empty string and abort this algorithm. Let private key be the generated priv…

…r q mod p (section 2.1.1). Also, X9.42 (which is referenced in section 2.3.3 of RFC3279) defines g as "generator of the q-order cyclic subgroup of GF(p), that is, an element of order q in the multiplicative group of GF(p)" (X9.42:2001, section 4.1) Errata ID: 4102 Status: Verifie…

…r q mod p (section 2.1.1). Also, X9.42 (which is referenced in section 2.3.3 of RFC3279) defines g as "generator of the q-order cyclic subgroup of GF(p), that is, an element of order q in the multiplicative group of GF(p)" (X9.42:2001, section 4.1) Errata ID: 4102 Status: Verifie…