Hello! We are running our annual fundraising. Please consider making a donation if you value this freely available service or want to support people around the world working towards liberatory social change. https://riseup.net/donate.

  1. 15 Dec, 2016 1 commit
  2. 15 Oct, 2016 5 commits
  3. 13 Oct, 2016 1 commit
  4. 12 Oct, 2016 3 commits
    • anarcat's avatar
      implement tor and SOCKS5 support · 0cf833c1
      anarcat authored
      implement Tor supports through a simple SOCKS5 client implemented with
      pysocks. --tor is basically a shortcut for --socks localhost:9050.
      
      we deliberately do not use the --use-tor flag of GPG 2.1 because we
      support legacy but also because supporting arbitrary SOCKS servers
      seems useful (e.g. SSH is a SOCKS proxy as well).
      
      there are no explicit tests for this, we delegate responsability for
      SOCKS tests to the pysocks library. integration errors would be our
      own, however, but i've tested this minimally and it seems to work,
      provided that the remote SMTP server doesn't blacklist Tor exit nodes
      (which is somewhat unlikely) or that the user knows a hidden service
      that his provider offers on the Tor network.
      
      Closes: #53
      0cf833c1
    • anarcat's avatar
      don't attempt STARTTLS over TLS connexions · 4ae1ffd6
      anarcat authored
      4ae1ffd6
    • anarcat's avatar
      skip relevant tests if keys have expired · d9a9a419
      anarcat authored
      we hardcode the expiry date for now, because we have a chicken and egg
      problem: to load the expiry dates, we need a working GPG library, and
      we are not so strong with expiration parsing yet, especially since
      there can be many expiration dates buried in subkeys, which I'm not
      confident we can parse.
      
      furthermore, the proper solution here is to remove expired keys from
      the test suite, but that is difficult for keys such as zack's that
      have very peculiar confugs.
      
      this allows us to re-enable tests in build as reproducible builds
      should just skip those tests now.
      
      it is useful to run tests in builds because it makes sure we run the
      test suite within the build environment. even though we run tests in
      the release process, that can be forgotten and may run in a different
      environment.
      d9a9a419
  5. 11 Oct, 2016 1 commit
  6. 04 Oct, 2016 2 commits
  7. 03 Oct, 2016 2 commits
  8. 02 Oct, 2016 2 commits
  9. 28 Sep, 2016 4 commits
  10. 26 Sep, 2016 1 commit
  11. 16 Sep, 2016 2 commits
  12. 31 Aug, 2016 1 commit
  13. 02 Dec, 2014 1 commit
  14. 21 Oct, 2014 1 commit
  15. 18 Oct, 2014 2 commits
  16. 17 Oct, 2014 1 commit
  17. 29 Aug, 2014 1 commit
  18. 20 Oct, 2013 1 commit
  19. 15 Oct, 2013 2 commits
  20. 05 Oct, 2013 3 commits
  21. 01 Oct, 2013 3 commits