Several people have asked me about how to rotate DKIM keys in the past few days (as if you’re modifying anything to mitigate replay attacks, you need to invalidate the signatures of all the mail you sent before you made those changes).
[icon name=”key” class=”2x spin”]
You really, really should be rotating your DKIM keys on a regular basis (monthly, weekly, quarterly?) in an automated way, so you shouldn’t need to be special-casing a change like this. Lots of people don’t, though, so here’s a quick summary of how to change your DKIM signing keys:
- Pick a new selector – either one that you’ve never used before, or (if you’re using ping-pong selectors) one that you’ve not used in the past week
- Generate a new key pair
- Add the new public key to your DNS servers
- Check that the new public key is visible on each of your public DNS servers
- Start signing outgoing mail with your new selector and new private key
- Wait 24 hours
- Delete the old public key from your DNS servers
DNS negative caching can cause some minor problems, if you’re not careful – if a DNS resolver queries for your public key before you’ve published it then it will cache that the key doesn’t exist for a short time. There are a few things to do to avoid that.
First, if you’re reusing a selector that you’ve ever used in the past then you should wait 24 hours after publishing the new public key before you start signing with the new private key. That will avoid having the nonexistent key cached at remote ISPs who happen to look it up based on an old message which used the same selector as your new keys.
Second, you shouldn’t manually look up the new public key in DNS before you know it’s published, so as to avoid you caching the nonexistent key in your own DNS caching resolver. That’ll cause mail you send to yourself or to other people at your company / ISP to fail DKIM validation, which is likely not a bad problem, but can make diagnosing signature failures difficult.
If you need to look for the key in DNS before it’s published (for example, to make sure that changes have published to your external DNS servers) you can avoid that by querying the authoritative servers directly (e.g. using @your.name.server with dig, or “host -t txt foo._domainkey.example.com your.name.server” with host).
You should probably avoid using web-based lookup tools to check your key records before they’re published too, for the same reason – but you can safely use our validation tools (as they only cache results for a maximum of sixty seconds).
Happy rotating!
[icon name=”key” class=”2x spin”]
RSS - Posts
The SMTP standards say that mail servers can take up to a week before timing out, so there is occasional mail that takes more than 24 hours to show up. I rotate monthly, create the new keys on the 27th of the previous month, rotate on the 1st, and delete the previous month’s keys on the 10th. This is probably overly conservative, but it’s been working fine for me.
[…] wanneer er ernstige kwetsbaarheden worden ontdekt in de gebruikte cryptografische standaarden. Op deze website kun je lezen hoe je de zogenaamde key rotation het beste kunt aanpakken. Daarnaast heb ik ontdekt […]