3 ms·
Seriously old news... I attacked Facebook's 512 bit DKIM key back in 2010: http://blog.jgc.org/2010/06/facebooks-dkim-rsa-key-should-be.html http://blog.jgc.org
by jgrahamc 14y ago
Seriously old news... I attacked Facebook's 512 bit DKIM key back in 2010: http://blog.jgc.org/2010/06/facebooks-dkim-rsa-key-should-be.html http://blog.jgc.org/2010/06/facebooks-dkim-rsa-key-should-be...
- dredge 14y agoI was just writing that! It was on HN too, of course: http://news.ycombinator.com/item?id=1442385 http://news.ycombinator.com/item?id=1442385 I was surprised then that anyone would be using a 512-bit RSA key in the wild, let alone now.
- Evbn 14y agoSo this is one key, used for all a domain's email for a long time, right? How lazy must you be to use an under specced key?
- jrabone 14y agoPlenty of crappy DNS web admin "tools" limit the maximum length of a TXT record. Sometimes it's harder than just typing "1024" instead of "512"...
- tptacek 14y agoI'm curious to hear what you think about DKIM in general.
- jgrahamc 14y agoAt one time DKIM and SPF were good indicators that an email was spam because spammers adopted it so that their mail looked more legit. I never look at DKIM or SPF. If I really care about who a message comes from I use PGP. It's a handy input for learning spam filters that use it as one piece of information, but it has about a 10% failure rate (legit mail where the signature fails to verify because of message manipulation in transit). It's most useful if the domain it's matching against is also trusted in some way. For example, a good signature against google.com is likely to mean the mail is good; a good signature against frohfuwehfwo.biz is not very helpful unless we know that that domain always sends spam. Also, the most important piece of mail I ever received (from the Prime Minister's office) came without SPF or DKIM and I authenticated it by calling the office. In general, external authentication like that tends to reassure me.