| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Implements the first half of #13060. The second half will be to remove
client support, too.
|
|
|
|
This implements the meat of #12899. This commit should simply remove the
parts of Tor dirauths used to check whether a relay was supposed to be
named or not, it doesn't yet convert to a new mechanism for
reject/invalid/baddir/badexiting relays.
|
|
|
|
Written by "NewEraCracker" on ticket 13081; I've added a note that
this is not our preferred or supported build method.
|
|
This is in preparation for a big patch series removing the entire Naming
system from Tor. In its wake, the approved-routers file is being
deprecated, and a replacement option to allow only pre-approved routers
is not being implemented.
|
|
|
|
|
|
|
|
|
|
We don't actually allow a group name, but the documentation implied
that we did.
|
|
When we merged the cookieauthfile creation logic in 33c3e60a37, we
accidentally took out this feature. Fixes bug 12864, bugfix on
0.2.5.1-alpha.
Also adds an ExtORPortCookieAuthFileGroupReadable, since there's no
reason not to.
|
|
|
|
|
|
|
|
This makes FastFirstHopPK an AUTOBOOL; makes the default "auto"; and
makes the behavior of "auto" be "look at the consensus."
|
|
|
|
|
|
|
|
|
|
* Issue #5583
|
|
Adds a note about using `make coverage-html` to generate coverage
reports.
Signed-off-by: Kevin Murray <spam@kdmurray.id.au>
|
|
|
|
I don't know whether we missed these or misclassified them when we
first made the "DIRECTORY AUTHORITY SERVER OPTIONS" section, but they
really belong there.
|
|
Our documentation had the name of this directory wrong.
|
|
See discussion on 9553: Some of the build scripts don't like it when
you can't merge maint into release.
|
|
(ticket 9553)
|
|
Conflicts:
src/or/config.c
|
|
|
|
|
|
|
|
Found with 'make check-docs'. Part of 11634.
|
|
|
|
We broke it when we added anchors to the manpage.
This patch fixes it, and makes it sorta detect missing anchors.
|
|
This basically amounts to grepping for every file that mentioned
contrib and adjusting its references to refer to the right place.
|
|
|
|
Conflicts:
src/or/main.c
|
|
If we can't detect the physical memory, the new default is 8 GB on
64-bit architectures, and 1 GB on 32-bit architectures.
If we *can* detect the physical memory, the new default is
CLAMP(256 MB, phys_mem * 0.75, MAX_DFLT)
where MAX_DFLT is 8 GB on 64-bit architectures and 2 GB on 32-bit
architectures.
You can still override the default by hand. The logic here is simply
trying to choose a lower default value on systems with less than 12 GB
of physical RAM.
|
|
This means that tor can run without needing to communicate with ioctls
to the firewall, and therefore doesn't need to run with privileges to
open the /dev/pf device node.
A new TransProxyType is added for this purpose, "pf-divert"; if the user
specifies this TransProxyType in their torrc, then the pf device node is
never opened and the connection destination is determined with getsockname
(as per pf(4)). The default behaviour (ie., when TransProxyType is "default"
when using the pf firewall) is still to assume that pf is configured with
rdr-to rules.
|
|
This isn't on by default; to get it, you need to set "TransProxyType
ipfw". (The original patch had automatic detection for whether
/dev/pf is present and openable, but that seems marginally fragile.)
|
|
|
|
We are searching @CONFDIR@ before $HOME, but the documentation
implied otherwise.
I screwed this up in f5e86bcd6c06d43ff3af5acd8135bd8b577bc3, when I
first documented the $HOME/.torrc possibility.
Fix for bug 9213; bugfix on 0.2.3.18-rc.
|
|
The build was broken by changes in f8c45339f72525c68, but we didn't
notice, since that commit also made torify.1 only get built when
tor-fw-helper was turned on.
Fixes bug 11321; bugfix on Tor 0.2.5.1-alpha.
|
|
|
|
In the end this required a slightly nasty hack using a dummy anchor as
an option heading in order to make the "Other recognized __flags__"
line indent properly.
Fixes bug 11061; Bugfix on 61d740ed.
|
|
|
|
|
