1. 11 Jul, 2019 2 commits
  2. 02 Apr, 2019 1 commit
  3. 29 Nov, 2017 1 commit
  4. 23 Aug, 2016 1 commit
  5. 10 Aug, 2016 1 commit
  6. 29 Apr, 2016 1 commit
  7. 30 Nov, 2015 1 commit
  8. 15 Feb, 2015 1 commit
    • Tails developers's avatar
      SSH client: don't proxy connections to 172.17.* to 172.31.*. · 6972d4fe
      Tails developers authored
      The RFC1918 172.16.0.0 range is a /12 one, while our previous configuration
      acted as if it was a /16 one, which left aside most of the addresses it should
      have covered.
      
      We've fixed that two years ago in the tsocks configuration (commit:35abfc62).
      For some reason, we've missed the same issue in the SSH client configuration
      back then.
      
      Will-fix: #6558
      6972d4fe
  9. 08 Sep, 2013 1 commit
    • Tails developers's avatar
      Use our custom connect-socks wrapper for SSH. · 1fe46967
      Tails developers authored
      Else, Tor 0.2.4's IsolateSOCKSAuth and connect-proxy sometimes play together in
      some way that makes connect-proxy ask for a password to connect to
      the SocksPort.
      
      Note that connect-socks uses the default SocksPort too, so no change here wrt.
      our connection isolation design.
      1fe46967
  10. 24 Jan, 2012 1 commit
  11. 02 Jan, 2012 2 commits
  12. 24 Nov, 2011 2 commits