1
0
Fork 1
mirror of https://github.com/NixOS/nixpkgs.git synced 2024-12-25 03:17:13 +00:00
Commit graph

188 commits

Author SHA1 Message Date
Thomas Gerbet 97368d3738 tor: 0.4.5.6 -> 0.4.5.7
Fixes CVE-2021-28089 and CVE-2021-28090.

Release notes:
https://blog.torproject.org/node/2009
2021-04-17 20:42:29 +02:00
Sandro Jäckel 3453b89f4b
lzma: deprecate alias 2021-04-04 19:49:52 +02:00
Pavol Rusnak 625413e723
tor: 0.4.4.7 -> 0.4.5.6 2021-02-15 21:27:07 +01:00
Pavol Rusnak 56f764720f
tor: 0.4.4.6 -> 0.4.4.7 2021-02-08 09:31:59 +01:00
Ben Siraphob 3bbad8b041 treewide: remove inherited stdenv.lib 2021-01-27 12:44:43 +07:00
Ben Siraphob 76f93cc731 pkgs/tools: pkgconfig -> pkg-config 2021-01-16 23:49:59 -08:00
Ben Siraphob 8c5d37129f pkgs/tools: stdenv.lib -> lib 2021-01-15 17:12:36 +07:00
Profpatsch 4a7f99d55d treewide: with stdenv.lib; in meta -> with lib;
Part of: https://github.com/NixOS/nixpkgs/issues/108938

meta = with stdenv.lib;

is a widely used pattern. We want to slowly remove
the `stdenv.lib` indirection and encourage people
to use `lib` directly. Thus let’s start with the meta
field.

This used a rewriting script to mostly automatically
replace all occurances of this pattern, and add the
`lib` argument to the package header if it doesn’t
exist yet.

The script in its current form is available at
https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2021-01-11 10:38:22 +01:00
Julien Moutinho 0ccdd6f2b0 nixos/tor: improve type-checking and hardening
Fixes #77395.
Fixes #82790.
2021-01-04 01:02:26 +01:00
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