1. 25 Sep, 2019 2 commits
  2. 01 Aug, 2019 2 commits
  3. 31 Jul, 2019 4 commits
  4. 29 May, 2019 1 commit
  5. 15 May, 2019 1 commit
    • updater: Implement prepare system · acf0f054
      As updater is used in environment, which requires it to have certificates
      available as fast as possible, add a prepare step and allow to launch it with
      --prepare-only switch.
      
      Thanks to this it is possible to run it with configuration file to provide
      fallback or master certificates for all slaves without connecting to the
      network, thus resulting in fast preparation.
      
      /reviewed-on !3
      Łukasz Nowak committed
  6. 14 May, 2019 1 commit
  7. 02 Apr, 2019 6 commits
  8. 12 Dec, 2018 1 commit
  9. 10 Dec, 2018 1 commit
  10. 07 Dec, 2018 1 commit
  11. 04 Dec, 2018 3 commits
  12. 27 Nov, 2018 1 commit
  13. 13 Nov, 2018 1 commit
    • KeDiFa: Initial implementation · f3a43056
      Provided tools are kedifa and kedifa-getter.
      
      kedifa is a server to PUT and GET sensitive information, like SSL keys and
      certificates.
      
      kedifa-getter is a client to this server.
      
      As both are closely related to caucase, they allow to use information from
      caucase, like CA Certificate, to validate each other.
      
      Caucase is also used to generate certificates for kedifa-getter used to
      authenticate to kedifa.
      
      Extracted important points of development of the inital version:
      
       * kedifa and kedifa-getter has been implemented
       * TODOs list is kept for future improvements
       * IPv6 and SSL-only support came
       * API has been docstring documented
       * PUTting information is based on query string key authorisation
       * GETting information requires SSL authentication
       * only correct keys are stored in KeDiFa database
       * certificates are served orderd by theirs submission date
       * kedifa-csr has been implemented, and dropped, as started to become openssl
         req implementation
       * caucase.http has been used as base for wsgiref approach
       * caucase.utils has been used for certificate management
       * argparse has been used for command line arguments
       * time comparison has been done in python, instead of SQLite
       * reloading, in caucase way, has been implemented
       * CRLs are in-app checked only, as pythons implementation does not allow
         proper reloads
       * in critical places code raises instead of returning False, in order to
         disallow ignoring result value
       * ids to store data has to be reserved
      Łukasz Nowak committed
  14. 03 Oct, 2018 1 commit