USC/ISI

ietf@hardakers.net

Performing DNSKEY algorithm transitions with DNSSEC signing is unfortunately challenging to get right in practice without decent tooling support. This document weighs the correct, completely secure way of rolling keys against an alternate, significantly simplified, method that takes a zone through an insecure state.

Performing DNSKEY algorithm transitions with DNSSEC signing is unfortunately challenging to get right in practice without decent tooling support. This document weighs the correct, completely secure way of rolling keys against an alternate, significantly simplified, method that takes a zone through an insecure state. Section 4.1.4 of describes the necessary steps required when a new signing key is published for a zone that uses a different signing algorithm than the currently published keys. These are the steps that MUST be followed when zone owners wish to have uninterrupted DNSSEC protection for their zones. The steps in this document are designed to ensure that all DNSKEY records and all DS records (and the rest of a zone records) are properly validatable by validating resolvers throughout the entire process. Unfortunately, there are a number of these steps that are challenging to accomplish either because the timing is tricky to get right or because current software doesn’t support automating the process easily. For example, the second step in Section 4.1.4 of requires that a new key with the new algorithm (which we refer to as K_new) be created, but not yet published. This step also requires that both the old key (K_old) and K_new sign and generate signatures for the zone, but with only the K_old key is published even though signatures from K_new are included. After this odd mix has been published for a sufficient time length, based on the TTL, can K_new be safely introduced and published into the zone as well. Although many DNSSEC signing solutions may automate the algorithm rollover steps (making operator involvement unnecessary), many other tools do not support automated algorithm updates. In these environments, the most challenging step is requiring that certain RRSIGs be published without the corresponding DNSKEYs that created them. This will likely require operators to use a text editor on the contents of a signed zone to carefully select zone records to extract before publication. This introduces potentially significant operator error(s). This document proposes an alternate, potentially more operationally robust but less secure, approach to performing algorithm DNSKEY rollovers for use in these situations.

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

An alternate approach to rolling DNSKEYs, especially when the toolsets being used do not provide easy algorithm rollover approaches, is to intentionally make the zone become insecure while the DNSKEYs and algorithms are swapped. At a high level, this means removing all DS records from the parent zone during the removal of the old key and the introduction of a new key using a new algorithm. Zone TTLs may be significantly shortened during this period to minimize the period of insecurity. Below are the enumerated steps required by this alternate transition mechanism. Note that there are still two critical waiting time requirements (steps 2 and 6) that must be followed carefully. Optional: lower the TTLs of the zone’s DS record (if possible) and the SOA’s negative TTL (MINIMUM) . Remove all DS records from the parent zone. Ensure the zone is considered unsigned by all validating resolvers by waiting 2 times the maximum TTL length for the DS record to expire from caches. This is the most critical timing. The author of this document failed to wait the required time once. It was not pretty. Replace the old DNSKEY(s) with the old algorithm with new DNSKEY(s) with the new algorithm(s) in the zone and publish the zone. Wait 2 times the zone SOA’s published negative cache time to ensure the new DNSKEYs will be found by validating resolvers. Add the DS record(s) for the new DNSKEYs to the parent zone. If the TTLs were modified in the optional step 1, change them back to their preferred values.

The process of replacing a DNSKEY with an older algorithm, such as RSAMD5 or RSASHA1 with a more modern one such as RSASHA512 or ECDSAP256SHA256 can be a daunting task if the zone’s current tooling doesn’t provide an easy-to-use solution. This is the case for zone owners that potentially use command line tools that are integrated into their zone production environment. This document describes an alternative approach to rolling DNSKEY algorithms that may be significantly less prone to operational mistakes. However, understanding of the security considerations of using this approach is paramount. The document recommends waiting 2 times TTL values in certain cases for added assurance that the waiting period is long enough for caches to expire. In reality, waiting only 1 TTL may be sufficient assuming all clocks around the world are operating with perfection.

DNSSEC provides an data integrity protection for DNS data. This document specifically calls out a reason why a zone owner may desire to deliberately turn off DNSSEC while changing the zone’s DNSKEY’s cryptographic algorithms. Thus, this is deliberately turning off security which is potentially harmful if an attacker knows when this will occur and can use that time window to launch DNS modification attacks (for example, cache poisoning attacks) against validating resolvers or other validating DNS infrastructure. Most importantly, this will deliberately break certain types of DNS records that must be validatable for them to be effective. This includes for example, but not limited to, all DS records for child zones, DANE , PGP keys , and SSHFP. Zone owners must carefully consider which records within their zone depend on DNSSEC being available before using the procedure outlined in this document. Given all of this, it leaves the question of: “why would a zone owner want to deliberately turn off security temporarily then?”, to which there is one principal answer. Simply put, if the the complexity of doing it the correct way is difficult with existing tooling then the chances of performing the more complex procedure and introducing an error, likely making the entire zone unavailable during that time period, may be significantly higher than the chances of the zone being attacked during the transition period of the simpler approach where zone availability is less likely to be impacted. Simply put, an invalid zone created by a botched algorithm roll is potentially worse than an unsigned but still available zone.

This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System. It obsoletes RFC-883. This memo documents the details of the domain name client - server communication. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. The Domain Name System Security Extensions (DNSSEC) add data origin authentication and data integrity to the Domain Name System. This document introduces these extensions and describes their capabilities and limitations. This document also discusses the services that the DNS security extensions do and do not provide. Last, this document describes the interrelationships between the documents that collectively describe DNSSEC. [STANDARDS-TRACK] This document is part of a family of documents that describe the DNS Security Extensions (DNSSEC). The DNS Security Extensions are a collection of new resource records and protocol modifications that add data origin authentication and data integrity to the DNS. This document describes the DNSSEC protocol modifications. This document defines the concept of a signed zone, along with the requirements for serving and resolving by using DNSSEC. These techniques allow a security-aware resolver to authenticate both DNS resource records and authoritative DNS error indications. This document obsoletes RFC 2535 and incorporates changes from all updates to RFC 2535. [STANDARDS-TRACK] This document specifies how to use the SHA-256 digest type in DNS Delegation Signer (DS) Resource Records (RRs). DS records, when stored in a parent zone, point to DNSKEYs in a child zone. [STANDARDS-TRACK] This document describes a set of practices for operating the DNS with security extensions (DNSSEC). The target audience is zone administrators deploying DNSSEC.The document discusses operational aspects of using keys and signatures in the DNS. It discusses issues of key generation, key storage, signature generation, key rollover, and related policies.This document obsoletes RFC 4641, as it covers more operational ground and gives more up-to-date requirements with respect to key sizes and the DNSSEC operations. RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. OpenPGP is a message format for email (and file) encryption that lacks a standardized lookup mechanism to securely obtain OpenPGP public keys. DNS-Based Authentication of Named Entities (DANE) is a method for publishing public keys in DNS. This document specifies a DANE method for publishing and locating OpenPGP public keys in DNS for a specific email address using a new OPENPGPKEY DNS resource record. Security is provided via Secure DNS, however the OPENPGPKEY record is not a replacement for verification of authenticity via the "web of trust" or manual verification. The OPENPGPKEY record can be used to encrypt an email that would otherwise have to be sent unencrypted. This document clarifies and updates the DNS-Based Authentication of Named Entities (DANE) TLSA specification (RFC 6698), based on subsequent implementation experience. It also contains guidance for implementers, operators, and protocol developers who want to use DANE records. This memo describes a downgrade-resistant protocol for SMTP transport security between Message Transfer Agents (MTAs), based on the DNS-Based Authentication of Named Entities (DANE) TLSA DNS record. Adoption of this protocol enables an incremental transition of the Internet email backbone to one using encrypted and authenticated Transport Layer Security (TLS). Encrypted communication on the Internet often uses Transport Layer Security (TLS), which depends on third parties to certify the keys used. This document improves on that situation by enabling the administrators of domain names to specify the keys used in that domain's TLS servers. This requires matching improvements in TLS client software, but no change in TLS server software. [STANDARDS-TRACK] This document describes a method of verifying Secure Shell (SSH) host keys using Domain Name System Security (DNSSEC). The document defines a new DNS resource record that contains a standard SSH key fingerprint. [STANDARDS-TRACK]

The author has discussed the pros and cons of this approach with multiple people, including Viktor Dukhovni and Warren Kumari.

While this document is under development, it can be viewed, tracked, issued, pushed with PRs, … here: https://github.com/hardaker/draft-hardaker-dnsop-intentionally-temporarily-insecure