RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)

Eastlake, Donald

doi:10.17487/rfc3110

Cited by 23 publications

(27 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The set of hash function, signature algorithm, and the algorithm used for generating the HIT from the HI depends on the HIT Suite (see Section 5. The RSA public key is encoded as defined in [RFC3110], Section 2, taking the exponent length (e_len), exponent (e), and modulus (n) fields concatenated. The length (n_len) of the modulus (n) can be determined from the total HI Length and the preceding HI fields including the exponent (e).…”

Section: Generating a Hit From An Himentioning

confidence: 99%

“…Thus, the data that serves as input for the HIT generation has the same length as the HI. The fields MUST be encoded in network byte order, as defined in [RFC3110].…”

Section: Generating a Hit From An Himentioning

confidence: 99%

“…The signature algorithms are defined in Section 5.2.9. The signature in the Signature field is encoded using the method depending on the signature algorithm (e.g., according to [RFC3110] in the case of RSA/ SHA-1, [RFC5702] in the case of RSA/SHA-256, [RFC2536] in the case of DSA, or [RFC6090] in the case of ECDSA).…”

Section: Hip_mac_2mentioning

confidence: 99%

See 2 more Smart Citations

Host Identity Protocol Version 2 (HIPv2)

Henderson¹,

Heer²,

Jokela³

et al. 2015

View full text Add to dashboard Cite

This document specifies the details of the Host Identity Protocol (HIP). HIP allows consenting hosts to securely establish and maintain shared IP-layer state, allowing separation of the identifier and locator roles of IP addresses, thereby enabling continuity of communications across IP address changes. HIP is based on a DiffieHellman key exchange, using public key identifiers from a new Host Identity namespace for mutual peer authentication. The protocol is designed to be resistant to denial-of-service (DoS) and man-in-themiddle (MitM) attacks. When used together with another suitable security protocol, such as the Encapsulating Security Payload (ESP), it provides integrity protection and optional encryption for upperlayer protocols, such as TCP and UDP.This document obsoletes RFC 5201 and addresses the concerns raised by the IESG, particularly that of crypto agility. It also incorporates lessons learned from the implementations of RFC 5201.

show abstract

Section: Generating a Hit From An Himentioning

confidence: 99%

“…Thus, the data that serves as input for the HIT generation has the same length as the HI. The fields MUST be encoded in network byte order, as defined in [RFC3110].…”

Section: Generating a Hit From An Himentioning

confidence: 99%

See 1 more Smart Citation

Host Identity Protocol Version 2 (HIPv2)

Henderson¹,

Heer²,

Jokela³

et al. 2015

View full text Add to dashboard Cite

show abstract

“…2 A RSA key is present, in the format defined in RFC 3110 [10]. The gateway field indicates a gateway to which an IPsec tunnel may be created in order to reach the entity named by this resource record.…”

Section: Rdata Format -Gateway Typementioning

confidence: 99%

“…The DSA key format is defined in RFC 2536 [9] The RSA key format is defined in RFC 3110 [10], with the following changes:…”

Section: Rdata Format -Public Keysmentioning

confidence: 99%