Age | Commit message (Collapse) | Author |
|
Make it possible to specify multiple ConsensusParams torrc
lines.
Now directory authority operators can for example put the
main ConsensusParams config in one torrc file and then add to it
from a different torrc file.
Closes ticket 40164.
|
|
|
|
This reverts commit bf2a399fc0d90df76e091fa3259f7c1b8fb87781.
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>
|
|
Make clear that Tor's C code targets C99 standards. This makes it more
explicit what to expect for new code, because guessing from existing
code is not always reliable, especially for code that predates the
change in standard.
|
|
|
|
Bugfix on 0.2.6.3-alpha; fixes bug 34299.
|
|
|
|
|
|
This change broke torsocks that by default is expecting an IPv4 for hostname
resolution because it can't ask tor for a specific IP version with the SOCKS5
extension.
PreferIPv6 made it that sometimes the IPv6 could be returned to torsocks that
was expecting an IPv4.
Torsocks is probably a very unique case because the runtime flow is that it
hijacks DNS resolution (ex: getaddrinfo()), gets an IP and then sends it back
for the connect() to happen.
The libc has DNS resolution functions that allows the caller to request a
specific INET family but torsocks can't tell tor to resolve the hostname only
to an IPv4 or IPv6 and thus by default fallsback to IPv4.
Reverting this change into 0.4.3.x series but we'll keep it in the 0.4.4.x
series in the hope that we add this SOCKS5 extension to tor for DNS resolution
and then change torsocks to use that.
Fixes #33804
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
Signed-off-by: David Goulet <dgoulet@torproject.org>
|
|
|
|
|
|
The default value of the option is "auto", not "default".
|
|
|
|
"proceeding" means starting an action.
"preceding" means the thing before this thing.
In this context, it's a bit ambiguous.
|
|
When making a new maint branch, stop running practracker in hooks.
|
|
* make end and beginning of life into second-level sections
* write an intro for beginning
* tweak intro for end
|
|
Re-applying changes after merge.
|
|
Ignored conflicting style changes: they will be re-applied in
the next commit.
|
|
|
|
Obviously correct documentation changes.
|
|
Updated 'doc/tor.1.txt' to match 'src/app/config/testnet.inc'.
|
|
|
|
It seems like this section is not valid anymore.
Most of this topics are already explained in different
files.
|
|
This approach doesn't require variable-length underlines.
|
|
|
|
Example:
.../doc/HACKING is now doc/HACKING
|
|
|
|
- external links use markdown's []() format,
- local files are formated with backquotes,
- duplicated new lines were removed,
- unnecesary single spaces were removed,
- broken links and local paths were updated.
|
|
|
|
And consistently talk about extra-info document publishing.
Obviously correct documentation changes.
|
|
|
|
Obviously correct changes to already-reviewed code.
|
|
|
|
|
|
|
|
|
|
|
|
Also, fix a typo.
|
|
|
|
|
|
|
|
- Fix a bug and add unittest.
- Add changes file.
- Add man page entry.
|
|
|
|
|
|
|
|
|
|
|
|
|