- 09 Jul, 2020 16 commits
-
-
Nick Mathewson authored
-
George Kadianakis authored
-
George Kadianakis authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
Nick Mathewson authored
-
David Goulet authored
When receiving an introduction NACK, the client either decides to close or re-extend the circuit to another intro point. In order to do this, the service descriptor needs to exists but it is possible that it gets removed from the cache between the establishement of the introduction circuit and the reception of the (N)ACK. For that reason, the BUG(desc == NULL) is removed because it is a possible normal use case. Tor recovers gracefully already. Fixes #34087 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
David Goulet authored
-
David Goulet authored
-
David Goulet authored
-
George Kadianakis authored
It now uses the 'goto err' pattern, instead of the fatal_unreached() pattern. The latter pattern is usually used when there is a loop, but there is no loop in this function so it can be simplified easily.
-
George Kadianakis authored
-
- 08 Jul, 2020 5 commits
-
-
This commit modifies the behavior of `parse_extended_address` in such a way that if it fails, it will always return a `BAD_HOSTNAME` value, which is then used to return the 0xF6 extended error code. This way, in any case that is not a valid v2 address, we return the 0xF6 error code, which is the expected behavior. Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
Alexander Færøy authored
-
Alexander Færøy authored
-
Alexander Færøy authored
-
Alexander Færøy authored
-
- 07 Jul, 2020 19 commits
-
-
Nick Mathewson authored
This warning only affects platforms (like win32) with 32-bit time_t. Fixes bug 40028; bugfix on 0.3.2.8-rc.
-
David Goulet authored
This reverts commit bf2a399f. Don't set by default the prefer IPv6 feature on client ports because it breaks the torsocks use case. The SOCKS resolve command is lacking a mechanism to ask for a specific address family (v4 or v6) thus prioritizing IPv6 when an IPv4 address is asked on the resolve SOCKS interface resulting in a failure. Tor Browser explicitly set PreferIPv6 so this should not affect the majority of our users. Closes #33796 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
Nick Mathewson authored
-
David Goulet authored
-
David Goulet authored
If no Address statement are found in the configuration file, attempt to learn our address by looking at the ORPort address if any. Specifying an address is optional so if we can't find one, it is fine, we move on to the next discovery mechanism. Note that specifying a hostname on the ORPort is not yet supported at this commit. Closes #33236 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
Alexander Færøy authored
-
Alexander Færøy authored
-
Alexander Færøy authored
-
Alexander Færøy authored
-
Nick Mathewson authored
Now that we have src/ext/ext.md (since b0a716df), we don't want to have src/ext excluded in its entirety. Like a smart person, when I added src/ext/ext.md, I edited Doxyfile, forgetting that it is generated from Doxyfile.in. :/ This should fix travis builds.
-
David Goulet authored
For some reasons, Appveyor started to use the stdio printf format for 64 bit values (PRIu64, ...). Mingw doesn't like that so force it to use the Windows specific macros by setting D__USE_MINGW_ANSI_STDIO=0. Fixes #40026
-
George Kadianakis authored
-
Nick Mathewson authored
-
-
-
-
-
-
-