about summary refs log tree commit diff
path: root/pkgs/tools/security/tor
Commit message (Collapse)AuthorAge
* tor: 0.4.2.7 -> 0.4.3.5R. RyanTM2020-05-24
|
* tor: fix cross compilingRichard Marko2020-05-04
|
* treewide: Per RFC45, remove all unquoted URLsMichael Reilly2020-04-10
|
* tor: 0.4.2.6 -> 0.4.2.7R. RyanTM2020-03-26
|
* tor: fix buildKonrad Borowski2020-02-19
| | | | | | | | | 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.
* tor: 0.4.2.5 -> 0.4.2.6R. RyanTM2020-02-10
|
* tor: patchShebangs script, fix buildWill Dietz2020-01-08
|
* tor: 0.4.1.6 -> 0.4.2.5Will Dietz2020-01-08
| | | | https://blog.torproject.org/new-release-0425-also-0417-0406-and-0359
* tor: 0.4.1.5 -> 0.4.1.6Will Dietz2019-09-19
| | | | https://blog.torproject.org/new-release-tor-0416
* Merge branch 'master' into staging-nextVladimír Čunát2019-08-24
|\ | | | | | | | | | | | | | | | | | | 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
| * tor: 0.4.0.5 -> 0.4.1.5Will Dietz2019-08-22
| | | | | | | | https://blog.torproject.org/new-release-tor-0415
* | treewide: name -> pname (easy cases) (#66585)volth2019-08-15
|/ | | | | | | | | treewide replacement of stdenv.mkDerivation rec { name = "*-${version}"; version = "*"; to pname
* tor: 0.3.5.7 -> 0.4.0.5Will Dietz2019-05-03
| | | | https://gitweb.torproject.org/tor.git/plain/ChangeLog?h=tor-0.4.0.5
* torsocks: 2.2.0 -> 2.3.0Will Dietz2019-01-15
| | | | https://github.com/dgoulet/torsocks/blob/v2.3.0/ChangeLog
* tor: 0.3.4.10 -> 0.3.5.7Will Dietz2019-01-08
| | | | (thank you, update script!)
* tor: lzma, zstd, scrypt depsWill Dietz2019-01-08
|
* tor: 0.3.4.9 -> 0.3.4.10Will Dietz2019-01-08
| | | | | | | | | | | | | 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" :).
* tor: 0.3.4.8 -> 0.3.4.9Will Dietz2018-11-02
| | | | | | | | 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.
* Merge remote-tracking branch 'upstream/master' into stagingJohn Ericson2018-09-18
|\
| * tor: 0.3.3.9 -> 0.3.4.8Joachim Fasting2018-09-11
| |
* | tor: disable parallel checkingJan Malakhovski2018-09-05
|/
* tor: fix failing Hydra buildMichishige Kaito2018-07-23
|
* pkgs/*: remove unreferenced function argumentsvolth2018-07-21
|
* tor: 0.3.3.8 -> 0.3.3.9Joachim Fasting2018-07-14
|
* tor: 0.3.3.7 -> 0.3.3.8R. RyanTM2018-07-10
| | | | 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.
* tor: 0.3.3.6 -> 0.3.3.7Joachim Fasting2018-06-12
|
* tor: 0.3.2.10 -> 0.3.3.6Joachim Fasting2018-05-23
| | | | First stable release in the 0.3.3.x series
* tor: initial updateScriptJoachim Fasting2018-03-04
| | | | | Tested briefly, seems to work okay. The gpg stuff could be better, however.
* tor: 0.3.2.9 -> 0.3.2.10Joachim Fasting2018-03-04
| | | | | Contains fixes for TROVE-2018-001, TROVE-2018-002, TROVE-2018-003, and TROVE-2018-004.
* tor: 0.3.1.9 -> 0.3.2.9Joachim Fasting2018-01-13
| | | | | | | - 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
* tor: 0.3.1.8 -> 0.3.1.9 (CVE-2017-{8819,8820,8821,8822,8823})Andreas Rammhold2017-12-03
| | | | | | More details in the release mail [1]. [1] https://lists.torproject.org/pipermail/tor-announce/2017-December/000147.html
* treewide: abandon Google Code homepagesc0bw3b2017-11-03
|
* tor: 0.3.1.7 -> 0.3.1.8Joachim Fasting2017-10-26
| | | | | | | | 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.
* tor: enable parallel buildingJoachim Fasting2017-09-22
|
* tor: 0.3.0.10 -> 0.3.1.7Joachim Fasting2017-09-19
|
* tor: 0.3.0.9 -> 0.3.0.10Joachim Fasting2017-08-02
| | | | | Fixes TPROXY on linux, fixes potential DOS on openbsd. Otherwise mostly minor bugfixes.
* tor: 0.3.0.8 -> 0.3.0.9Joachim Fasting2017-07-01
| | | | See https://blog.torproject.org/blog/tor-0309-released-security-update-clients
* tor: 0.3.0.7 -> 0.3.0.8Joachim Fasting2017-06-09
| | | | | | | 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
* tor: 0.3.0.6 -> 0.3.0.7Joachim Fasting2017-05-16
| | | | | Contains a fix for TROVE-2017-002, a remotely triggered crashing bug affecting tor relays (clients & releases pre 0.3.0 unaffected).
* tor: 0.2.9.10 -> 0.3.0.6Joachim Fasting2017-04-27
| | | | | | First stable release in the 0.3 series. https://blog.torproject.org/blog/tor-0306-released-new-series-stable
* torbrowser: reduce risk of stale Nix store referencesJoachim Fasting2017-03-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* torbrowser: 6.5 -> 6.5.1Joachim Fasting2017-03-08
|
* tor: split out geoip dataJoachim Fasting2017-03-02
| | | | | | | | | | | 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
* tor: 0.2.9.9 -> 0.2.9.10Joachim Fasting2017-03-01
| | | | | | | | | | | | 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.
* gst-plugins-base: align attrname with pkgnameBjørn Forsman2017-02-27
|
* gst-plugins-good: align attrname with pkgnameBjørn Forsman2017-02-27
|
* gst-ffmpeg: align attrname with pkgnameBjørn Forsman2017-02-27
|
* torbrowser: make additional media playback support optionalJoachim Fasting2017-01-28
| | | | | | | This feature might not be appropriate for all users, leave it off by default. See 96be6a11a85e9e253cf733e57ce7c67fd1a3b81c
* torbrowser: fix url typoJoachim Fasting2017-01-26
| | | | | | | I used nix-prefetch-url to generate the hashes, so of course this mistake slipped by ... Ref: 5bbe54272de8689f7bdb2071d528e5d961edadda
* torbrowser: 6.0.8 -> 6.5Joachim Fasting2017-01-26
| | | | | | | Updates to firefox-esr 45.7, which fixes several critical vulnerabilities [1] [1]: https://www.mozilla.org/en-US/security/advisories/mfsa2017-02/
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-06-26 16:08:27 +0000