1. 22 Jan, 2016 3 commits
    • Patrick J Cherry's avatar
      common: Updated changelog · 92109e85
      Patrick J Cherry authored
      92109e85
    • Patrick J Cherry's avatar
      common: Made sure that the next set name returns a sane answer · 4ce169ca
      Patrick J Cherry authored
      It has to check all the directories in sets/ to pick the next, not just
      use the next name of the "last" available set.
      4ce169ca
    • Patrick J Cherry's avatar
      common: Refactored how --force works and when certs get generated/rolled over · ddc32981
      Patrick J Cherry authored
      The defaults are as follows:
      
      * If the current set is available
      
      ** If it is due to expire inside the threshold
      
      *** generate a new set if there is no set more recent (unless instructed
      otherwise)
      *** roll over to the new set if one has been generated (unless
      instructed not to)
      
      ** Otherwise
      
      *** do not generate a new set (unless instructed otherwise)
      *** do not roll over (unless instructed to)
      
      * If the "current" set is missing, but other sets are available
      
      ** If the most recent set is due to expire inside the threshold
      
      *** generate a new set (unless instructed otherwise)
      *** roll over to the new set if one has been generated (unless
      instructed not to)
      
      ** If the most recent set is not due to expire soon
      
      *** do not generate a new set (unless instructed otherwise)
      *** roll over to the latest set (unless instructed not to)
      
      * If there are no certificate sets
      
      ** generate a new one (unless instructed otherwise)
      ** roll over to the new set if one has been generate (unless instructed
      not to)
      ddc32981
  2. 21 Jan, 2016 16 commits
  3. 19 Jan, 2016 2 commits
  4. 15 Jan, 2016 1 commit
  5. 14 Jan, 2016 15 commits
  6. 13 Jan, 2016 1 commit
  7. 12 Jan, 2016 2 commits