Commit graph

179 commits

Author SHA1 Message Date
Pavol Rusnak 4c0678ca9a
tor: 0.4.4.5 -> 0.4.4.6 2020-11-17 19:43:19 +01:00
Chris Double b1c43525d0 tor: remove myself as maintainer 2020-11-09 11:44:51 +00:00
Pavol Rusnak c1ed88eaee
tor: 0.4.3.6 -> 0.4.4.5 2020-10-03 23:02:53 +02:00
John Wiegley ef3cb36ba4
torsocks: Fix the Darwin build 2020-08-06 15:52:54 -07:00
Mario Rodas e71c525eb7
Merge pull request #94077 from mweinelt/tor
tor: passthru tests
2020-07-28 16:53:48 -05:00
Martin Weinelt a24694a90d
tor: passthru tests 2020-07-28 15:16:37 +02:00
R. RyanTM 90007b56e8 tor: 0.4.3.5 -> 0.4.3.6 2020-07-15 04:06:39 +00:00
R. RyanTM 906323f0de tor: 0.4.2.7 -> 0.4.3.5 2020-05-24 14:55:26 +00:00
Richard Marko 8aab081504 tor: fix cross compiling 2020-05-04 14:27:40 +02:00
Michael Reilly 84cf00f980
treewide: Per RFC45, remove all unquoted URLs 2020-04-10 17:54:53 +01:00
R. RyanTM 21900acf6d tor: 0.4.2.6 -> 0.4.2.7 2020-03-26 03:32:21 +00:00
Konrad Borowski 58af3177c0 tor: fix build
Monotonic timer test expects sleep(200ms) to take at most 1s. On
loaded systems like hydra, it's possible for such a test to take
longer than 1 second.

Tests expecting sleep(200ms) to take at least 175ms weren't removed,
because load shouldn't cause sleep to be shorter.
2020-02-19 09:11:46 +01:00
R. RyanTM 6a64f267a0 tor: 0.4.2.5 -> 0.4.2.6 2020-02-10 19:43:58 +01:00
Will Dietz bd712ef6c3
tor: patchShebangs script, fix build 2020-01-08 15:55:09 -06:00
Will Dietz 48838ac958
tor: 0.4.1.6 -> 0.4.2.5
https://blog.torproject.org/new-release-0425-also-0417-0406-and-0359
2020-01-08 15:54:57 -06:00
Will Dietz 855d3e7eaf
tor: 0.4.1.5 -> 0.4.1.6
https://blog.torproject.org/new-release-tor-0416
2019-09-19 09:48:50 -05:00
Vladimír Čunát 2e6bf42a22
Merge branch 'master' into staging-next
There ver very many conflicts, basically all due to
name -> pname+version.  Fortunately, almost everything was auto-resolved
by kdiff3, and for now I just fixed up a couple evaluation problems,
as verified by the tarball job.  There might be some fallback to these
conflicts, but I believe it should be minimal.

Hydra nixpkgs: ?compare=1538299
2019-08-24 08:55:37 +02:00
Will Dietz 65f5e4512c
tor: 0.4.0.5 -> 0.4.1.5
https://blog.torproject.org/new-release-tor-0415
2019-08-22 13:21:58 -05:00
volth 46420bbaa3 treewide: name -> pname (easy cases) (#66585)
treewide replacement of

stdenv.mkDerivation rec {
  name = "*-${version}";
  version = "*";

to pname
2019-08-15 13:41:18 +01:00
Will Dietz 0d5e0da42d tor: 0.3.5.7 -> 0.4.0.5
https://gitweb.torproject.org/tor.git/plain/ChangeLog?h=tor-0.4.0.5
2019-05-03 02:02:31 -05:00
Will Dietz fcb4d11757 torsocks: 2.2.0 -> 2.3.0
https://github.com/dgoulet/torsocks/blob/v2.3.0/ChangeLog
2019-01-15 15:24:55 -06:00
Will Dietz 6b3943d07d tor: 0.3.4.10 -> 0.3.5.7
(thank you, update script!)
2019-01-08 21:31:28 -06:00
Will Dietz 5db46cf3f1 tor: lzma, zstd, scrypt deps 2019-01-08 21:31:27 -06:00
Will Dietz 91859c0504 tor: 0.3.4.9 -> 0.3.4.10
https://lists.torproject.org/pipermail/tor-announce/2019-January/000171.html

FWIW, in the ChangeLog (in the source, sorry) it mentions:

  As a reminder, the Tor 0.3.4 series will be supported until 10 June
  2019. Some time between now and then, users should switch to the Tor
  0.3.5 series, which will receive long-term support until at least 1
  Feb 2022.

So we should consider moving to 0.3.5 "soon" :).
2019-01-08 21:31:25 -06:00
Will Dietz c78761b5bd tor: 0.3.4.8 -> 0.3.4.9
https://gitweb.torproject.org/tor.git/plain/ChangeLog?h=tor-0.3.4.9

Please confirm the sha256 is correct for a verified tarball,
I'm not setup (or know how offhand but docs look promising)
to do this myself.
2018-11-02 13:21:25 -05:00
John Ericson 7319013ea1 Merge remote-tracking branch 'upstream/master' into staging 2018-09-18 16:55:42 -04:00
Joachim Fasting 48abf865bc
tor: 0.3.3.9 -> 0.3.4.8 2018-09-11 14:44:10 +02:00
Jan Malakhovski e48f2d0226 tor: disable parallel checking 2018-09-05 01:14:40 +00:00
Michishige Kaito f66ad737a4 tor: fix failing Hydra build 2018-07-23 14:54:32 +01:00
volth 52f53c69ce pkgs/*: remove unreferenced function arguments 2018-07-21 02:48:04 +00:00
Joachim Fasting 08144faaac
tor: 0.3.3.8 -> 0.3.3.9 2018-07-14 22:50:36 +02:00
R. RyanTM f0aea0cc1b tor: 0.3.3.7 -> 0.3.3.8
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/tor/versions.
2018-07-10 21:30:58 -07:00
Joachim Fasting e701948f5a
tor: 0.3.3.6 -> 0.3.3.7 2018-06-12 22:33:33 +02:00
Joachim Fasting 1c14927d69
tor: 0.3.2.10 -> 0.3.3.6
First stable release in the 0.3.3.x series
2018-05-23 21:49:14 +02:00
Joachim Fasting 9c0e9f6a30
tor: initial updateScript
Tested briefly, seems to work okay. The gpg stuff could be better,
however.
2018-03-04 23:47:01 +01:00
Joachim Fasting e4581f05e4
tor: 0.3.2.9 -> 0.3.2.10
Contains fixes for TROVE-2018-001, TROVE-2018-002, TROVE-2018-003, and
TROVE-2018-004.
2018-03-04 13:12:49 +01:00
Joachim Fasting 87677d0390
tor: 0.3.1.9 -> 0.3.2.9
- Adds next-generation onion services[1]
- Lots of fixes, e.g., for CVE-2017-8821, CVE-2017-8820, CVE-2017-8823,
  CVE-2017-8819, CVE-2017-8822, CVE-2017-8822
- Adds new option `NoExec` to disallow exec syscalls
2018-01-13 18:22:45 +01:00
Andreas Rammhold 959364c01d
tor: 0.3.1.8 -> 0.3.1.9 (CVE-2017-{8819,8820,8821,8822,8823})
More details in the release mail [1].

[1] https://lists.torproject.org/pipermail/tor-announce/2017-December/000147.html
2017-12-03 20:35:16 +01:00
c0bw3b 525380b472 treewide: abandon Google Code homepages 2017-11-03 18:52:28 +00:00
Joachim Fasting 5a64e446ff
tor: 0.3.1.7 -> 0.3.1.8
Quoth the release notes:

> It includes several bugfixes, including a bugfix for a crash issue that
had affected relays under memory pressure. It also adds a new directory
authority, Bastet.
2017-10-26 22:39:24 +02:00
Joachim Fasting fd3a9e6468
tor: enable parallel building 2017-09-22 22:37:15 +02:00
Joachim Fasting 1ee60e98e2
tor: 0.3.0.10 -> 0.3.1.7 2017-09-19 02:36:38 +02:00
Joachim Fasting 4751fca48c
tor: 0.3.0.9 -> 0.3.0.10
Fixes TPROXY on linux, fixes potential DOS on openbsd.
Otherwise mostly minor bugfixes.
2017-08-02 20:05:05 +02:00
Joachim Fasting d7ce6a83b1
tor: 0.3.0.8 -> 0.3.0.9
See https://blog.torproject.org/blog/tor-0309-released-security-update-clients
2017-07-01 13:37:37 +02:00
Joachim Fasting 8e706b051e
tor: 0.3.0.7 -> 0.3.0.8
Of particular note are fixes for hidden service crashing bugs
(TROVE-2017-004 and TROVE-2017-005).

See https://blog.torproject.org/blog/tor-0308-released-fix-hidden-services-also-are-02429-02514-02612-0278-02814-and-02911
2017-06-09 00:40:25 +02:00
Joachim Fasting 3cd189c3bc
tor: 0.3.0.6 -> 0.3.0.7
Contains a fix for TROVE-2017-002, a remotely triggered crashing bug
affecting tor relays (clients & releases pre 0.3.0 unaffected).
2017-05-16 11:14:14 +02:00
Joachim Fasting 7301bf8581
tor: 0.2.9.10 -> 0.3.0.6
First stable release in the 0.3 series.

https://blog.torproject.org/blog/tor-0306-released-new-series-stable
2017-04-27 19:26:59 +02:00
Joachim Fasting ecd0e1a2c7
torbrowser: reduce risk of stale Nix store references
This patch restructures the expression and wrapper to minimize Nix store
references captured by the user's state directory.

The previous version would write lots of references to the Nix store into
the user's state directory, resulting in synchronization issues between
the Store and the local state directory.  At best, this would cause TBB to
stop working when the version used to instantiate the local state was
garbage collected; at worst, a user would continue to use the old version
even after an upgrade.

To solve the issue, hard-code as much as possible at the Store side and
minimize the amount of stuff being copied into the local state dir.
Currently, only a few files generated at firefox startup and fontconfig
cache files end up capturing store paths; these files are simply removed
upon every startup.  Otherwise, no capture should occur and the user
should always be using the TBB associated with the tor-browser wrapper
script.

To check for stale Store paths, do
   `grep -Ero '/nix/store/[^/]+' ~/.local/share/tor-browser`
This command should *never* return any other store path than the one
associated with the current tor-browser wrapper script, even after an
update (assuming you've run tor-browser at least once after updating).
Deviations from this general rule are considered bugs from now on.

Note that no attempt has been made to support pluggable transports; they
are still broken with this patch (to be fixed in a follow-up patch).

User visible changes:
- Wrapper retains only environment variables required for TBB to work
- pulseaudioSupport can be toggled independently of mediaSupport (the
  latter weakly implies the former).
- Store local state under $TBB_HOME.  Defaults to $XDG_DATA_HOME/tor-browser
- Stop obnoxious first-run stuff (NoScript redirect, in particular)
- Set desktop item GenericName to Web Browser

Some minor enhancements:
- Disable Hydra builds
- Specify system -> source mapping to make it easier to
  extend supported platforms.
2017-03-25 15:59:18 +01:00
Joachim Fasting 74f8e0fd7a
torbrowser: 6.5 -> 6.5.1 2017-03-08 20:08:46 +01:00
Joachim Fasting c44a41c73f
tor: split out geoip data
Saves about 5.2 MiB.

To use geoip, add something like
```
GeoIPFile ${tor.geoip}/share/tor/geoip
GeoIPv6File ${tor.geoip}/share/tor/geoip6
```
to torrc
2017-03-02 12:40:33 +01:00