summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2021-09-17one more pass over the changelogtor-0.4.7.1-alphaRoger Dingledine
2021-09-17Run format_changelog.Nick Mathewson
2021-09-17Edit changelog with a few grammar and simplicity fixes.Nick Mathewson
2021-09-17Bump version to 0.4.7.1-alphaDavid Goulet
Signed-off-by: David Goulet <dgoulet@torproject.org>
2021-09-17changelog: ChangeLog for 0.4.7.1-alpha releaseDavid Goulet
Signed-off-by: David Goulet <dgoulet@torproject.org>
2021-09-16Merge remote-tracking branches 'tor-gitlab/mr/439' and 'tor-gitlab/mr/441'Nick Mathewson
2021-09-15Update Tor's man 1 pageskaluzka
Add few missing periods, convert tabs to spaces. No new significant content added. Signed-off-by: skaluzka <skaluzka@protonmail.com>
2021-09-14tor.1 man page: Add mention of fingerprint-ed25519, and clarify differencesNeel Chauhan
2021-09-13Merge branch 'maint-0.4.6'David Goulet
2021-09-13Merge branch 'maint-0.4.5' into maint-0.4.6David Goulet
2021-09-13Merge branch 'maint-0.3.5' into maint-0.4.5David Goulet
2021-09-13Only check for bindable ports if we are unsure if it will fail.Alexander Færøy
We currently assume that the only way for Tor to listen on ports in the privileged port range (1 to 1023), on Linux, is if we are granted the NET_BIND_SERVICE capability. Today on Linux, it's possible to specify the beginning of the unprivileged port range using a sysctl configuration option. Docker (and thus the CI service Tor uses) recently changed this sysctl value to 0, which causes our tests to fail as they assume that we should NOT be able to bind to a privileged port *without* the NET_BIND_SERVICE capability. In this patch, we read the value of the sysctl value via the /proc/sys/ filesystem iff it's present, otherwise we assume the default unprivileged port range begins at port 1024. See: tor#40275
2021-09-13Use Debian bullseye for our hardened build.Alexander Færøy
2021-09-13Force amd64 for CI builds.Alexander Færøy
2021-09-08Clear asciidoc-helper.sh syntaxskaluzka
Remove all unnecessary ";" characters at the end of several lines. Align all indentations to 4 spaces. Update console messages related to XML_CATALOG_FILES and .bashrc file. Signed-off-by: skaluzka <skaluzka@protonmail.com>
2021-09-07Align and fix indentations in several maint scriptsskaluzka
Use 4 spaces indentations, convert tabs to spaces. No real code changes.
2021-09-07Merge remote-tracking branch 'tor-gitlab/mr/426'Nick Mathewson
2021-08-31Merge branch 'tor-gitlab/mr/424'David Goulet
2021-08-29Improve fname_is_c func in pratracker/includes.pyskaluzka
Use tuples for bname.startswith and fname.endswith in "fname_is_c" function.
2021-08-26Add spaces between the "and" when logging the "Your server has not managed ↵Neel Chauhan
to confirm reachability for its" on dual-stack relays
2021-08-26Add reference implementation for ntor v3.Nick Mathewson
2021-08-26Initial backend for an ntor-v3 implementation.Nick Mathewson
This code is based directly on the specification, without looking at the reference implementation or the implementation in Arti. Nonetheless, it is now passing with the test vectors generated by the reference implementation.
2021-08-26Remove changes files that have already been in changelogs for 0.4.6Nick Mathewson
2021-08-22Correct syntax & formatting in test_pratracker.shskaluzka
Use 4 spaces for indentations. Use the same syntax for all functions. No real code changes (except removal of unnecessary ";" from "exit 1" command).
2021-08-18Merge remote-tracking branch 'tor-gitlab/mr/420'Nick Mathewson
2021-08-18Merge remote-tracking branch 'tor-gitlab/mr/419'Nick Mathewson
2021-08-17dir: Do not flag non-running failing HSDirDavid Goulet
When a directory request fails, we flag the relay as non Running so we don't use it anymore. This can be problematic with onion services because there are cases where a tor instance could have a lot of services, ephemeral ones, and keeps failing to upload descriptors, let say due to a bad network, and thus flag a lot of nodes as non Running which then in turn can not be used for circuit building. This commit makes it that we never flag nodes as non Running on a onion service directory request (upload or fetch) failure as to keep the hashring intact and not affect other parts of tor. Fortunately, the onion service hashring is _not_ selected by looking at the Running flag but since we do a 3-hop circuit to the HSDir, other services on the same instance can influence each other by removing nodes from the consensus for path selection. This was made apparent with a small network that ran out of nodes to used due to rapid succession of onion services uploading and failing. See #40434 for details. Fixes #40434 Signed-off-by: David Goulet <dgoulet@torproject.org>
2021-08-16Forward merge the latest ChangeLog/ReleaseNotesDavid Goulet
Signed-off-by: David Goulet <dgoulet@torproject.org>
2021-08-16Merge branch 'maint-0.4.6'David Goulet
2021-08-16Merge branch 'maint-0.4.5' into maint-0.4.6David Goulet
2021-08-16Bump version to -devDavid Goulet
Signed-off-by: David Goulet <dgoulet@torproject.org>
2021-08-16Merge branch 'maint-0.3.5' into maint-0.4.5David Goulet
2021-08-16Bump version to -devDavid Goulet
Signed-off-by: David Goulet <dgoulet@torproject.org>
2021-08-16Bump version to -devDavid Goulet
Signed-off-by: David Goulet <dgoulet@torproject.org>
2021-08-16Merge branch 'maint-0.4.6' into mainAlexander Færøy
2021-08-16Merge branch 'maint-0.4.5' into maint-0.4.6Alexander Færøy
2021-08-16Always teardown capture of logs in CAPTURE().Alexander Færøy
This will hopefully solve an issue where our gmtime related tests are failing on 32-bit builds.
2021-08-16Merge branch 'maint-0.4.6' into mainAlexander Færøy
2021-08-16Merge branch 'maint-0.4.5' into maint-0.4.6Alexander Færøy
2021-08-16Merge branch 'maint-0.3.5' into maint-0.4.5Alexander Færøy
2021-08-16Use debian:buster instead of debian:stable for now.Alexander Færøy
2021-08-16Merge branch 'maint-0.4.6'Nick Mathewson
2021-08-16Merge branch 'maint-0.4.5' into maint-0.4.6Nick Mathewson
2021-08-16Disable message checking for some 32-bit tests about timegm failure.Nick Mathewson
Since we merged 40383, we don't expect these to give the same warning on every platform.
2021-08-16Merge branch 'maint-0.4.6'Nick Mathewson
"ours" to avoid version bump.
2021-08-16Make the version 0.4.6.7, not 0.4.6.7-dev.Nick Mathewson
2021-08-16Merge branch 'maint-0.4.5' into maint-0.4.6Nick Mathewson
"ours" to avoid version bump
2021-08-16Make the version 0.4.5.10, not 0.4.5.10-dev.Nick Mathewson
2021-08-16Merge branch 'maint-0.3.5' into maint-0.4.5Nick Mathewson
"ours" to avoid version bump
2021-08-16Make the version 0.3.6.16, not 0.3.6.16-dev.Nick Mathewson
7apu2bq3rhoylwmucxizk54afw5jyda7pho4j5zdcqpwkufke7zdzwad.onion