1. 06 Apr, 2017 1 commit
  2. 05 Apr, 2017 1 commit
  3. 04 Apr, 2017 2 commits
  4. 05 Mar, 2017 1 commit
  5. 02 Mar, 2017 7 commits
  6. 05 Nov, 2016 1 commit
  7. 16 Oct, 2016 5 commits
  8. 11 Sep, 2016 1 commit
  9. 08 Sep, 2016 2 commits
  10. 24 Aug, 2016 3 commits
  11. 17 Aug, 2016 2 commits
  12. 16 Aug, 2016 1 commit
  13. 12 Aug, 2016 4 commits
    • Adrien Dorsaz's avatar
    • Adrien Dorsaz's avatar
      Remove useless imports · 75c7a594
      Adrien Dorsaz authored
      75c7a594
    • Adrien Dorsaz's avatar
      style: apply some pep8 recommandations · da492ff5
      Adrien Dorsaz authored
      da492ff5
    • Adrien Dorsaz's avatar
      selfcheck: check if DNS has been correctly updated before asking ACME to check DNS records · 4ef84e71
      Adrien Dorsaz authored
      This check use the DNS server defined in DNS section (Host setting).
      
      For each host, the script will :
      1. push update to the DNS host
      2. wait delay configured in seconds with parameter CheckChallengeDelay
      3. ask the DNS host for TXT entries corresponding to the challenge
      4. check if at least one entry corresponds to the key authorization
          * if there's one, let ask to the acme server to check themselves
          * if there's none:
              * wait 2 seconds and retry from step 3 (retry 10 times)
      5. If after 10 retries nothing happend, stop with error
      
      So, we have this behavior:
      * if user knows its setup has no bottleneck and won't apply delay before checks,
         he sets CheckChallengeDelay to 0.
      * if user knows there's some bottleneck for DNS update, it can set CheckChallengeDelay
         to a specific amount of seconds
      
      In both case, the script will ensure it won't bother the ACME server with useless
      operations.
      4ef84e71
  14. 28 Jun, 2016 6 commits
  15. 29 Dec, 2015 1 commit
  16. 22 Dec, 2015 2 commits