On Sun, Oct 27, 2024 at 06:40:06PM +0000, Pete Long via mailop wrote:
> The issue has now been resolved. I'm not entirely sure how but all
> I've done on my end is to generate a new pair of DKIM keys today and
> pop the public key in DNS for valar.uk.net.
The new key encoding has no internal whitespace (which SHOULD have been
ignored, but perhaps wasn't). If this was indeed the issue at Gmail
their implementation is out of spec and should be made more resilient.
$ dig +short -t txt default._domainkey.valar.uk.net |
perl -lpe '
s/\A"|"\z//g;
s{([^\\"]+)|\\\d{3}|\\(.)|" "}{"$1$3".($2?chr(int($2)):"")}eg;
s/.*?;\s+p\s*=\s*//; s/;.*//
'
"v=DKIM1; k=rsa;
p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtWeIDz1pdmR1f4ZIs2SOOoXkMaYu0iOnHzPoJpZ2xwvT8uFLauG6IfkIEtZwFJ/t9R2qq6fdrn9YT3GhkEgWOM6o6dFpfxqqtQXtwaExHGIIf7EPG2m2WM+LZpkBRjl60FpE4BKwrGbaxdBJ3i1XYiGaNElFcRkvdj+pWxPd6/AL9O3a5IxdXuoQ7qaC0St20"
"TYXjTdQx0dlAp3HU4MLletOBei6YzlfDYwvKtDbiavP6i3MwVI3qfxOs1UqvVXiKcrrdGzM44YqGnpGkstAhkDO/5XRUVES/anCqyjCyfhfoHjfVeo35ThxP99D2aZ+vVVoRtqR8D2xWIGA1PpcAQIDAQAB#"
Mind you, why is there a trailing "#" at the end of the "p=" value,
that's not a valid Base64 character, and is not expected here. The
correct encoding is without the trailing "#":
"v=DKIM1; k=rsa;
p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAtWeIDz1pdmR1f4ZIs2SOOoXkMaYu0iOnHzPoJpZ2xwvT8uFLauG6IfkIEtZwFJ/t9R2qq6fdrn9YT3GhkEgWOM6o6dFpfxqqtQXtwaExHGIIf7EPG2m2WM+LZpkBRjl60FpE4BKwrGbaxdBJ3i1XYiGaNElFcRkvdj+pWxPd6/AL9O3a5IxdXuoQ7qaC0St20"
"TYXjTdQx0dlAp3HU4MLletOBei6YzlfDYwvKtDbiavP6i3MwVI3qfxOs1UqvVXiKcrrdGzM44YqGnpGkstAhkDO/5XRUVES/anCqyjCyfhfoHjfVeo35ThxP99D2aZ+vVVoRtqR8D2xWIGA1PpcAQIDAQAB"
--
Viktor.
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
