From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 3/4] Tor: Do not try to support IPv6 for Directory and OR ports
Date: Sat, 25 Sep 2021 09:08:42 +0200 [thread overview]
Message-ID: <37a388ab-a01e-6628-f872-d5db530d7688@ipfire.org> (raw)
In-Reply-To: <37079e43-a5af-db04-086e-750f04151b75@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
We currently don't have IPv6 in vanilla IPFire 2.x installations, hence
there is no sense in letting Tor finding out IPv6 connectivity.
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
html/cgi-bin/tor.cgi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/html/cgi-bin/tor.cgi b/html/cgi-bin/tor.cgi
index 2b0d93336..8ecef5d9c 100644
--- a/html/cgi-bin/tor.cgi
+++ b/html/cgi-bin/tor.cgi
@@ -802,10 +802,10 @@ sub BuildConfiguration() {
# Reject access to private networks.
print FILE "ExitPolicyRejectPrivate 1\n";
- print FILE "ORPort $settings{'TOR_RELAY_PORT'}\n";
+ print FILE "ORPort $settings{'TOR_RELAY_PORT'} IPv4Only\n";
if ($settings{'TOR_RELAY_DIRPORT'} ne '0') {
- print FILE "DirPort $settings{'TOR_RELAY_DIRPORT'}\n";
+ print FILE "DirPort $settings{'TOR_RELAY_DIRPORT'} IPv4Only\n";
}
if ($settings{'TOR_RELAY_ADDRESS'} ne '') {
--
2.26.2
next prev parent reply other threads:[~2021-09-25 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 7:07 [PATCH 1/4] Tor: Enable syscall sandbox Peter Müller
2021-09-25 7:08 ` [PATCH 2/4] Tor: Use crypto hardware acceleration if available Peter Müller
2021-09-25 7:08 ` Peter Müller [this message]
2021-09-25 7:09 ` [PATCH 4/4] Tor: Bump package version Peter Müller
2021-09-27 18:46 ` [PATCH 2/4] Tor: Use crypto hardware acceleration if available Michael Tremer
2021-10-04 10:49 ` Peter Müller
2021-10-04 13:59 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37a388ab-a01e-6628-f872-d5db530d7688@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox