From: ng0 <ng0@infotropique.org>
To: 27862@debbugs.gnu.org
Subject: bug#27862: tor-hidden-service should support IPv6
Date: Sun, 30 Jul 2017 09:09:31 +0000 [thread overview]
Message-ID: <20170730090931.ajkzp55femqauh62@abyayala> (raw)
In-Reply-To: <20170728154652.tgigkve7n5wzdrlc@abyayala>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
ng0 transcribed 1.3K bytes:
> Right now the tor-hidden-service only supports IPv4 naming scheme,
> while it is possible to define IPv6 for tor aswell.
>
> Someone should fix this.
man tor:
HIDDEN SERVICE OPTIONS
The following options are used to configure a hidden service.
…
HiddenServicePort VIRTPORT [TARGET]
Configure a virtual port VIRTPORT for a hidden service. You may use this option multiple times; each
time applies to the service using the most recent HiddenServiceDir. By default, this option maps the
virtual port to the same port on 127.0.0.1 over TCP. You may override the target port, address, or
both by specifying a target of addr, port, addr:port, or unix:path. (You can specify an IPv6 target as
[addr]:port. Unix paths may be quoted, and may use standard C escapes.) You may also have multiple
lines with the same VIRTPORT: when a user connects to that VIRTPORT, one of the TARGETs from those
lines will be chosen at random.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
https://www.infotropique.org https://krosos.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-07-30 9:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 15:46 bug#27862: tor-hidden-service should support IPv6 ng0
2017-07-30 9:09 ` ng0 [this message]
2017-08-02 22:07 ` Ludovic Courtès
2017-08-02 22:45 ` ng0
2017-08-04 21:54 ` Ludovic Courtès
2017-10-20 16:03 ` Ludovic Courtès
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=20170730090931.ajkzp55femqauh62@abyayala \
--to=ng0@infotropique.org \
--cc=27862@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.