I found a unique error in DK-FILTER 1.0.1 when the DNS TXT record contains more than beginning and ending quotes.
Williams & Sonoma newsletter email:
;; QUESTION SECTION:
;williamssonoma._domainkey.enews.williams-sonoma.com. IN TXT
;; ANSWER SECTION:
williamssonoma._domainkey.enews.williams-sonoma.com. 3600 IN TXT "g=*\; k=rsa\; t=y\; n=" "Contact" "email@example.com" "with" "any" "questions" "concerning" "this" "signing" "\; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDaktaU8E6joTYJEOKQRcKMbgE7Xt8lg/Y3ZQGQCS+MpjAoR5KEJBogaS9ke1ilCcGBy+zT+LBxrgDPmszP5ewrXLNmkThViIIU6FZa5WbthZXlnCwVoYUlUG1XESDlruXBFayUgQVjXBregIaZ3uC77I6jCjPHfRhn9neDdeKP4wIDAQAB\;"
As you can see the above DNS query, the administrator has taken some liberty in creating instructions through the use of multiple double quotations.
The DK-FILTER response I get is:
Oct 13 12:35:03 ns1 dk-filter: m9DGYunp016718: bad signature data
It appears that DK-FILTER cannot correctly parse the correct key when there are multiple beginning/ending quotes.
I believe the administrator is probably in error, but DK-FILTER should account for this during its parse.
Log in to post a comment.