| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
| |
Fixes CVE-2021-28089 and CVE-2021-28090.
Release notes:
https://blog.torproject.org/node/2009
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
Fixes #77395.
Fixes #82790.
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
tor: passthru tests
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
https://blog.torproject.org/new-release-0425-also-0417-0406-and-0359
|
|
|
|
| |
https://blog.torproject.org/new-release-tor-0416
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| | |
https://blog.torproject.org/new-release-tor-0415
|
|/
|
|
|
|
|
|
|
| |
treewide replacement of
stdenv.mkDerivation rec {
name = "*-${version}";
version = "*";
to pname
|
|
|
|
| |
https://gitweb.torproject.org/tor.git/plain/ChangeLog?h=tor-0.4.0.5
|
|
|
|
| |
https://github.com/dgoulet/torsocks/blob/v2.3.0/ChangeLog
|
|
|
|
| |
(thank you, update script!)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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" :).
|
|
|
|
|
|
|
|
| |
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.
|
|\ |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
First stable release in the 0.3.3.x series
|
|
|
|
|
| |
Tested briefly, seems to work okay. The gpg stuff could be better,
however.
|
|
|
|
|
| |
Contains fixes for TROVE-2018-001, TROVE-2018-002, TROVE-2018-003, and
TROVE-2018-004.
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
| |
More details in the release mail [1].
[1] https://lists.torproject.org/pipermail/tor-announce/2017-December/000147.html
|
| |
|
|
|
|
|
|
|
|
| |
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.
|