1. 16 Jul, 2015 6 commits
  2. 06 Jul, 2015 1 commit
    • Helga Velroyen's avatar
      Write SSH ports to ssconf files · d657fadc
      Helga Velroyen authored
      For the downgrading of the SSL setup from 2.12 to 2.11, we
      need to be able to SSH into machines while no daemons are
      running. Unfortunately currently the only way to obtain
      custom-configured SSH ports is by queries. In order to
      access this information with daemons being shutdown, this
      patch adds the SSH port information to an ssconf file.
      
      This will also be used to simplify some backend calls for
      the *SSH* handling in 2.13.
      Signed-off-by: default avatarHelga Velroyen <helgav@google.com>
      Reviewed-by: default avatarPetr Pudlak <pudlak@google.com>
      d657fadc
  3. 16 Jun, 2015 3 commits
  4. 15 Jun, 2015 2 commits
  5. 12 Jun, 2015 1 commit
  6. 01 Jun, 2015 1 commit
  7. 29 May, 2015 1 commit
  8. 27 May, 2015 2 commits
  9. 21 May, 2015 1 commit
  10. 07 May, 2015 1 commit
    • Hrvoje Ribicic's avatar
      Modify UDS server startup to set permissions for sockets · c7c42554
      Hrvoje Ribicic authored
      When opening domain sockets for communication, the Haskell daemons did
      not set any permissions for the sockets, defaulting to 0700. This was
      fine when all of them ran as root, but was bound to cause trouble in a
      split-user setup. The first issue is RAPI access after master-failover,
      where RAPI could not send make any inquiries until the watcher restored
      the desired permissions of the socket.
      
      This patch modifies Luxid to use a g+rw socket, and leaves other servers
      to their default of 0600.
      Signed-off-by: default avatarHrvoje Ribicic <riba@google.com>
      Reviewed-by: default avatarKlaus Aehlig <aehlig@google.com>
      c7c42554
  11. 06 May, 2015 2 commits
  12. 28 Apr, 2015 2 commits
  13. 22 Apr, 2015 2 commits
  14. 21 Apr, 2015 1 commit
  15. 17 Apr, 2015 1 commit
  16. 08 Apr, 2015 1 commit
    • Klaus Aehlig's avatar
      Make writeConfigAndUnlock retryable · 5dafcf36
      Klaus Aehlig authored
      We have the built-in assumption that daemons can be restarted
      at any time. This includes situations where an action is already
      taken, but the caller did not get the answer jet. For the case
      of writeConfigAndUnlock this can lead to the command being reissued;
      of course, it should not do anything on second attempt, but fail in
      a way the caller can live with.
      Signed-off-by: default avatarKlaus Aehlig <aehlig@google.com>
      Reviewed-by: default avatarPetr Pudlak <pudlak@google.com>
      5dafcf36
  17. 24 Mar, 2015 6 commits
  18. 05 Mar, 2015 1 commit
  19. 16 Feb, 2015 1 commit
  20. 09 Jan, 2015 1 commit
  21. 11 Nov, 2014 3 commits