- Oct 24, 2019
-
-
teor authored
Bionic has a recent coccinelle version, which passes our CI tests. But Bionic (and Xenial) cause permissions errors for chutney. We'll fix those in 32240. Part of 31919.
-
- Oct 22, 2019
- Oct 17, 2019
-
-
teor authored
-
- Oct 02, 2019
-
-
Karsten Loesing authored
-
- Sep 30, 2019
-
-
teor authored
Since Travis macOS has IPv6 support (and Travis Linux does not), chutney will now run its IPv6 networks as part of Travis CI. But since chutney is slow, don't wait for the macOS chutney to finish. (Travis have fixed the duplicate notification bug in fast_finish. So we can use fast_finish and allow_failure to finish early. Unfortunately, allow_failure also means we ignore failures in macOS chutney.) Also make sure that we have: * a compile on each platform, with each compiler, * a check on each platform, and * a check on each compiler. Finally, sort builds: allow fail last, macOS first, slowest first. Closes ticket 30860. Closes ticket 31859 for 0.2.9.
-
teor authored
Part of 31859.
-
- Sep 26, 2019
-
-
teor authored
The jobs should be the same, but Travis may display them differently. Part of 31859.
-
- Sep 23, 2019
-
-
Nick Mathewson authored
Frequently, when a patch fails, it has failures in several files. Using the "-k" flag will let us learn all the compilation errors, not just the first one that the compiler hits. Based on a patch by rl1987.
-
- Sep 18, 2019
-
-
Nick Mathewson authored
-
- Sep 09, 2019
-
-
David Goulet authored
Closes #31673
-
- Aug 15, 2019
-
-
David Goulet authored
New IP address from 194.109.206.212 to 45.66.33.45. Signed request from Alex de Joode, operator of dizum: https://trac.torproject.org/projects/tor/ticket/31406 Published descriptor by dizum on August 12th, 2019: -- r dizum fqbq1v2DCDxTj0QDi7+gd1h911U GZmZtCLaPDQNxkhIFj8UcgTRAuA 2019-08-12 15:28:40 45.66.33.45 443 80 s Authority Fast Running Stable V2Dir Valid v Tor 0.4.0.5 pr Cons=1-2 Desc=1-2 DirCache=1-2 HSDir=1-2 HSIntro=3-4 HSRend=1-2 Link=1-5 LinkAuth=1,3 Microdesc=1-2 Relay=1-2 Padding=1 w Bandwidth=20 Unmeasured=1 p reject 1-65535 -- Finally, confirmed by DNS: $ dig +short tor.dizum.com 45.66.33.45 Closes #31406 Signed-off-by:
David Goulet <dgoulet@torproject.org>
-
- Aug 09, 2019
- Aug 08, 2019
-
-
teor authored
-
teor authored
-
Nick Mathewson authored
Fixes bug 31374; bugfix on 0.2.9.1-alpha.
-
Nick Mathewson authored
-
Nick Mathewson authored
My previous fix removed a comparison, which would have caused us to warn about every skew instead of skews of over an hour.
-
-
teor authored
-
teor authored
-
- Aug 06, 2019
-
-
Nick Mathewson authored
On some windows builds, time_t is 64 bits but long is not. This is causing appveyor builds to fail. Also, one of our uses of labs() on time_t was logically incorrect: it was telling us to accept NETINFO cells up to three minutes _before_ the message they were responding to, which doesn't make sense. This patch adds a time_abs() function that we should eventually move to intmath.h or something. For now, though, it will make merges easier to have it file-local in channeltls.c. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
-
- Jul 19, 2019
-
-
Nick Mathewson authored
-
Overflowing a signed integer in C is an undefined behaviour. It is possible to trigger this undefined behaviour in tor_asprintf on Windows or systems lacking vasprintf. On these systems, eiter _vscprintf or vsnprintf is called to retrieve the required amount of bytes to hold the string. These functions can return INT_MAX. The easiest way to recreate this is the use of a specially crafted configuration file, e.g. containing the line: FirewallPorts AAAAA<in total 2147483610 As> This line triggers the needed tor_asprintf call which eventually leads to an INT_MAX return value from _vscprintf or vsnprintf. The needed byte for \0 is added to the result, triggering the overflow and therefore the undefined behaviour. Casting the value to size_t before addition fixes the behaviour. Signed-off-by:
Tobias Stoeckmann <tobias@stoeckmann.org>
-
- Jul 01, 2019
- Jun 28, 2019
-
-
teor authored
Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc in December 2018 (of which ~122 were still functional), with a list of 148 fallbacks (70 new, 78 existing, 79 removed) generated in June 2019. Closes ticket 28795. Note that we created extra lists from DE and US, but they didn't add any more fallbacks when we tried to merge them.
-
teor authored
Update the fallback directory mirrors by merging the current list with: fallback_dirs_2019-06-28-08-58-39_AU_f0437a39ddbc8459.inc Part of 28795, see that ticket for logs.
-
teor authored
Update the fallback directory mirrors by replacing the old list with: fallback_dirs_2019-06-25-11-49-10_AU_a37adb956fbb5cd2.inc Part of 28795, see that ticket for logs.
-
- Jun 12, 2019
-
-
Nick Mathewson authored
-
Nick Mathewson authored
Previously we had "make check" launched whenever DISTCHECK was false. Now we'd like to turn it off in a few other circumstances, like running chutney. Maybe stem too?
-
- Jun 11, 2019
-
-
Karsten Loesing authored
-