JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
265,104 Commits 2 Branches 0 Tags 12 GiB
35aac20463
Commit Graph

86 Commits

Author SHA1 Message Date
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
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
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
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
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
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
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
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
Joachim Fasting
05054e34c0
tor: 0.2.9.9 -> 0.2.9.10 
The 0.2.9 series is now a long-term support release, which will
receive backported security fixes until at least 2020.

tor should now build against libressl, as in
```nix
tor.override { openssl = libressl; }
```

Also re-enable the test-suite; works fine on my end.
 2017-03-01 23:56:34 +01:00
Joachim Fasting
bdfe638f31
tor: 0.2.8.12 -> 0.2.9.9 2017-01-25 00:58:37 +01:00
Joachim Fasting
3e92b56be3
tor: 0.2.8.10 -> 0.2.8.12 
Notably contains fix for CVE-2016-1254

cc @grahamc
 2016-12-19 23:49:17 +01:00
Joachim Fasting
d06bf820ea
tor: 0.2.8.9 -> 0.2.8.10 
Per upstream, this contains primarily stability & performance fixes.
Notably, the relase fixes a bug that would sometimes make clients
unusable after leaving standby mode, as well as plugging a memory leak.
 2016-12-03 07:17:13 +01:00