2016
DOI: 10.17487/rfc7929
|View full text |Cite
|
Sign up to set email alerts
|

DNS-Based Authentication of Named Entities (DANE) Bindings for OpenPGP

Abstract: 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 a… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
10
0
1

Year Published

2017
2017
2022
2022

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 14 publications
(15 citation statements)
references
References 10 publications
1
10
0
1
Order By: Relevance
“…Note that the information returned in the SMIMEA record might be for the end entity certificate, or it might be for the trust anchor or an intermediate certificate. This mechanism is similar to the one given in [RFC7929] for OpenPGP.…”
Section: The Smimea Resource Recordsupporting
confidence: 79%
See 2 more Smart Citations
“…Note that the information returned in the SMIMEA record might be for the end entity certificate, or it might be for the trust anchor or an intermediate certificate. This mechanism is similar to the one given in [RFC7929] for OpenPGP.…”
Section: The Smimea Resource Recordsupporting
confidence: 79%
“…This document describes a mechanism for associating a user's certificate with the domain that is similar to that described in DANE itself [RFC6698], as updated by [RFC7218] and [RFC7671]; it is also similar to the mechanism given in [RFC7929] for OpenPGP. Most of the operational and security considerations for using the mechanism in this document are described in RFC 6698 and are not described here at all.…”
Section: Rfc 8162 Dns-based Authentication For S/mimementioning
confidence: 99%
See 1 more Smart Citation
“…Traditionally, this was done using dedicated key/certificate servers, LDAP servers, etc., but these methods are not always easy to deploy and standardize for every enterprise. �ese certificates can be published through the DNS by a different implementation of the DANE mechanism for S/MIME [RFC8162] and OpenPGP [RFC7929]. S/MIME and OpenPGP, with their strengthening by DANE authentication are discussed below.…”
Section: End-to-end Authentication Using S/mime Digital Signaturesmentioning
confidence: 99%
“…A renewed interest in personal control over email authentication and encryption has led to further work within the IETF on key sharing, and the DANE mechanism [RFC7929] is being adopted to place a domain and user's public key in an OPENPGPKEY record in the DNS. Unlike DANE/TLS and SMIMEA, OPENPGPKEY does not use X.509 certificates, or require full PKIX authentication as an option.…”
Section: Openpgp and Openpgpkeymentioning
confidence: 99%