1. 06 Apr, 2016 3 commits
    • Steve Kemp's avatar
      Document why directory-traversal attacks will fail. · a38058e2
      Steve Kemp authored
      I tested this too.
      a38058e2
    • Steve Kemp's avatar
      Minor comment updating. · b7c3ef06
      Steve Kemp authored
      b7c3ef06
    • Steve Kemp's avatar
      Replace the Ruby logger process with a golang version. · 893599a8
      Steve Kemp authored
      This code is functionally identical to the Ruby version, all being
      well, and barring bugs.
      
      The intention is that we can allow users to install this package
      if they're at all suffering with issues with RAM usage.  This is
      deliberately taken as a safe middle-ground before rewriting a core
      component of symbiosis and forcing all users to upgrade at once.
      
      Once this package is installed the old ruby-based logger will be
      divered, via dpkg-divert, such that it is no longer in use and
      can be replaced.
      
      Removign this package undoes the diversion to restore the system
      to that state it was previously in.
      
      This updates #12663.
      893599a8
  2. 24 Feb, 2016 1 commit
  3. 16 Feb, 2016 2 commits
  4. 05 Feb, 2016 2 commits
  5. 04 Feb, 2016 2 commits
    • Patrick J Cherry's avatar
      backup: Updated changelog · f9c6802c
      Patrick J Cherry authored
      f9c6802c
    • Patrick J Cherry's avatar
      backups: Updated the bacup2l.conf parsing in the available space check · b264fcd5
      Patrick J Cherry authored
      Although the diff is quite large, the changes are as follows:
      
      * Allow a backup2l.conf to be specified as an argument
      * A reguar expression is used to find the BACKUP_DIR definition
      * More error checking around the running of the backup2l estimate
      * The two regexes parsing the output have been squashed into one.
      * When the estimate was just Bytes, the parsing failed, as a space was
        in between the number and the letter B.
      b264fcd5
  6. 03 Feb, 2016 4 commits
  7. 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
  8. 21 Jan, 2016 16 commits
  9. 19 Jan, 2016 2 commits
  10. 15 Jan, 2016 1 commit
  11. 14 Jan, 2016 4 commits