1. 11 Mar, 2018 2 commits
  2. 23 Jan, 2018 2 commits
  3. 30 Dec, 2017 1 commit
  4. 29 Dec, 2017 1 commit
  5. 28 Dec, 2017 4 commits
  6. 19 Dec, 2017 3 commits
  7. 10 Aug, 2017 1 commit
  8. 11 May, 2017 7 commits
  9. 11 Apr, 2017 2 commits
  10. 10 Apr, 2017 1 commit
  11. 08 Apr, 2017 4 commits
  12. 04 Apr, 2017 3 commits
  13. 03 Apr, 2017 2 commits
  14. 02 Apr, 2017 2 commits
    • Ram-Z's avatar
      Fix directory creation · c3606b31
      Ram-Z authored
      c3606b31
    • Ram-Z's avatar
      Set GNUPGHOME inside the chroot · 2a8fe8b1
      Ram-Z authored
      gnupg is weird:
      
      1. It behaves differently when run with fakeroot, try
      ```
      $ GNUPGHOME=~/.gnupg gpgconf --list-dirs socketdir
      /run/user/1000/gnupg
      $ GNUPGHOME=~/.gnupg fakeroot gpgconf --list-dirs socketdir
      ~/.gnupg
      ```
      
      2. It behaves differently when GNUPGHOME is set, unset or set to the
         default value.
      ```
      $ gpgconf --list-dirs socketdir
      /run/user/1000/gnupg
      $ GNUPGHOME=/tmp gpgconf --list-dirs socketdir
      /tmp
      $ GNUPGHOME=~/.gnupg gpgconf --list-dirs socketdir
      /run/user/1000/gnupg
      ```
      2a8fe8b1
  15. 01 Apr, 2017 2 commits
    • Ram-Z's avatar
      Use actual user id · 2cbb56d9
      Ram-Z authored
      I had assumed that the user in the chroot was always created with id
      1000, but it's actually using the id of the hosts user.
      2cbb56d9
    • Ram-Z's avatar
      Use proper agent forwarding · 8288da74
      Ram-Z authored
      There should be no need for mounting GNUPGHOME into the chroot which
      should help with keeping private keys private.
      8288da74
  16. 11 Mar, 2017 1 commit
  17. 13 Feb, 2017 1 commit
  18. 07 Feb, 2017 1 commit