Joshua Tauberer 6d4fab1e6a whats_next: offer DNSSEC DS parameters rather than the full record and in validation allow for other digests than the one we suggest using ...

fixes #120 (hopefully), in which Gandi generates a SHA1 digest but we were only checking against a SHA256 digest

Also see http://discourse.mailinabox.email/t/how-to-set-ds-record-for-gandi-net/24/1 in which a user asks about the DS parameters that Gandi asks for.

2014-08-01 12:15:05 +00:00

..

templates

move management into a daemon service running as root

2014-06-03 13:56:40 +00:00

auth.py

Cleanup: remove env dependency

2014-06-22 08:55:19 -04:00

backup.py

increase duplicity's volume size from the default of 25MB to 100MB so we create fewer files

2014-06-09 13:47:41 +00:00

buy_certificate.py

check that the installed certificate corresponds to the private key

2014-07-08 15:47:54 +00:00

daemon.py

add a --force flag to dns_update

2014-08-01 12:05:34 +00:00

dns_update.py

whats_next: offer DNSSEC DS parameters rather than the full record and in validation allow for other digests than the one we suggest using

2014-08-01 12:15:05 +00:00

mailconfig.py

re-do catch-all aliases, fixes #107 (originally #104)

2014-07-13 12:29:43 +00:00

utils.py

utils.sort_domains wasn't right

2014-07-09 12:35:12 +00:00

web_update.py

dont serve web for domains with custom DNS records that point A/AAAA elsewhere, and in whats_next only check that an A record exists on a domain if we are serving web on the domain

2014-07-20 15:23:17 +00:00

whats_next.py

whats_next: offer DNSSEC DS parameters rather than the full record and in validation allow for other digests than the one we suggest using

2014-08-01 12:15:05 +00:00