Missing k= should default to "rsa" in DKIM TXT record #2

New issue

Closed

opened 2026-09-05 11:55:49 +00:00 by steve · 0 comments

steve commented

2026-09-05 11:55:49 +00:00

Owner

k= Key type (plain-text; OPTIONAL, default is "rsa"). Signers and
Verifiers MUST support the "rsa" key type. The "rsa" key type
indicates that an ASN.1 DER-encoded [ITU-X660-1997] RSAPublicKey
(see [RFC8017], Sections 3.1 and A.1.1) is being used in the "p="
tag. (Note: the "p=" tag further encodes the value using the
base64 algorithm.) In addition Signers and Verifiers SHOULD
support the "ed25519" key type (See [RFC8463]). The p= value in
the key record is the Ed25519 public key encoded in base64.
Unrecognized key types MUST be ignored.

(from Raademar https://github.com/turscar/dkim2/issues/4)

k= Key type (plain-text; OPTIONAL, default is "rsa"). Signers and Verifiers MUST support the "rsa" key type. The "rsa" key type indicates that an ASN.1 DER-encoded [ITU-X660-1997] RSAPublicKey (see [RFC8017], Sections 3.1 and A.1.1) is being used in the "p=" tag. (Note: the "p=" tag further encodes the value using the base64 algorithm.) In addition Signers and Verifiers SHOULD support the "ed25519" key type (See [RFC8463]). The p= value in the key record is the Ed25519 public key encoded in base64. Unrecognized key types MUST be ignored. (from Raademar https://github.com/turscar/dkim2/issues/4)

steve added the

bug

label

2026-09-05 11:55:49 +00:00

steve self-assigned this

2026-09-05 11:55:49 +00:00

steve referenced this issue from a commit

2026-09-05 16:32:52 +00:00

If no k= is provided in a public key record, default to "rsa". Closes #2.

steve closed this issue

2026-09-05 16:32:52 +00:00