tor-hidden-service should support IPv6

  • Done
  • quality assurance status badge
Details
2 participants
  • Ludovic Courtès
  • ng0
Owner
unassigned
Submitted by
ng0
Severity
normal
N
N
ng0 wrote on 28 Jul 2017 17:46
(address . bug-guix@gnu.org)
20170728154652.tgigkve7n5wzdrlc@abyayala
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.
--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAll7XGwACgkQ4i+bv+40
hYgybRAAp7fcEjhLFvdviqoUUSjFPddBeju+dS2hB9lj1ru2haIfuO1nS9ZhSGQs
1tGcuIPgelRT0jez7ZzHaNlCQPaE2vuUiklcubsUws8yx4KVCzPoPJa3JeKJmwUR
M2En2PyYB6037Yr0CPctqO6UgiPlqtqdBwIA2QhiVdYgoUNvJcLoqtieHe6shoUa
V3ml4vqpFxCv9MBDZZx1fG1ya/XLbsYq9Chwdp6O1oBclzKMubckYpdSQJF2Af1D
M4mPBnn1qJdbqIcEw7axtcK4JuLUBXlDtpugwUr4AptmlmDubtyE0CiZklTuCQDt
Z/NpxQvGl3Q1cICa0sKOXOuTKr5TIMdOZUWJD63iD+n5+nY5yxW1pGuoatGPGrNI
z8vkwesXnqAHloonRY84XeFy+tOJlxWRqQJ6Ghjngty399+3j3s9vwtLsZEfJnci
TlmtszKT87uij9SiI0mUGk0W7VeROcuGjkTga3qpq7v1JKKuCqxfG54wu93l9+PP
2BVi0+WWgQBjzwGgNcST+DyX5qP55mHuo78Ql4jhW/WczW66LISXZInvmf1+4uhZ
KYC3moRz7MKo7Lp/JJyCitVIGTjNUPhmD7BOG9PfZokIz6eapRFTFRYKtHu/i3qJ
J4JhbW/xZn2viKvlDPBLWewIu4Y4dbzacHllsecKAtargZ1+VJU=
=p8qr
-----END PGP SIGNATURE-----


N
N
ng0 wrote on 30 Jul 2017 11:09
(address . 27862@debbugs.gnu.org)
20170730090931.ajkzp55femqauh62@abyayala
ng0 transcribed 1.3K bytes:
Toggle quote (5 lines)
> 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
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAll9oksACgkQ4i+bv+40
hYhiBQ//UNWIhYy8Z+kRE1rwpVX99SLezyZ68YBMXUi/e2tRC4bHx1cV+LGNztOe
Q2RCmtlFTcTgZUvlcmoOTMrjtaEuSdkTGYuaHyRYWVZ+s+3vSEbHaGLbSP7KrxlR
8s0UAvNIg/B1TutLPeTPOLyo3BBoXIKPyTPSUinZ998aTAqoj8v6HhLJCth9ny2e
KAh5caTCuscuhfc9P184LKOIvukmzNeN+wIIf8C7Z2vCbilJMVuOBtRk9Jk+xdIM
FtrJ3FU/0FI59thAW7U+NQiqGpqNxlANJWn1jmWXJPDSmUw7HxNSfgNFeUxD9V86
nu5fVU2DH9NmhdcgYfyY9211gNRS9xy5/xA2adVbqJCQTTHB+bspMbnAs8U9Iue6
XSUYPM0zQ9N3DN7o/eMit+KVzdsrJ6kxCEaV+rXS0Hei6qViXwnZehOzigZWOkO9
qHYHdv1F1Ct8yErvUoZ93BdTSmvQUPtR5BlizzpdYYtQzwku1yI2RxgHu+pIYmqz
iF4RobbrazBzxXTgV/ER6EwsEHlKwQTIZj6HgTghJqp9lV8Us578k97ob7Y9pALc
9dlzKVt0YflqfOSiJ2S2mPUB9tH2+IDwtONp7GZMuV9WtFFsIcEpNeT8+r57uqyT
kr1bP/fcplOWzuTtU6CG2FiL1W6LuYrxyVPNrimxfzIkLcijz6A=
=jXye
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 3 Aug 2017 00:07
(name . ng0)(address . ng0@infotropique.org)(address . 27862@debbugs.gnu.org)
87a83hsjws.fsf@gnu.org
ng0 <ng0@infotropique.org> skribis:

Toggle quote (3 lines)
> Right now the tor-hidden-service only supports IPv4 naming scheme,
> while it is possible to define IPv6 for tor aswell.

‘tor-hidden-service’ does not interpret addresses. So one could write,
say:

(80 . "[::1]:80")

and that’d be IPv6 (talking to localhost over IPv6 is great ;-)).
It is what you had in mind?

Toggle quote (2 lines)
> Someone should fix this.

I agree, someone!

Thanks,
Ludo’.
N
N
ng0 wrote on 3 Aug 2017 00:45
(name . Ludovic Courtès)(address . ludo@gnu.org)
20170802224505.coaewqkh7p5dqhum@abyayala
Ludovic Courtès transcribed 0.4K bytes:
Toggle quote (10 lines)
> ng0 <ng0@infotropique.org> skribis:
>
> > Right now the tor-hidden-service only supports IPv4 naming scheme,
> > while it is possible to define IPv6 for tor aswell.
>
> ‘tor-hidden-service’ does not interpret addresses. So one could write,
> say:
>
> (80 . "[::1]:80")

Oh. Okay, I did not even try it because I live on the dark side of IPv6 ;)
Then all which needs to be done is a small extension of the documentation
of tor-hidden-service.

Toggle quote (11 lines)
> and that’d be IPv6 (talking to localhost over IPv6 is great ;-)).
> It is what you had in mind?
>
> > Someone should fix this.
>
> I agree, someone!
>
> Thanks,
> Ludo’.
>

--
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEqIyK3RKYKNfqwC5S4i+bv+40hYgFAlmCVfEACgkQ4i+bv+40
hYhx6w//Y3iOQ4B2ZMFGt3bEWT6tikQsrngiP5Hf1xKkVdvRN8OuKU60kAKXIgH8
ZZ2yf0Q4pt6SZ0lNJYs1yg8STkj78sKE4Xq2vMVMVGsG7IsZoE1rTOtWeBDf9NYl
FMzW390f8/5TduBWfWXmkoLy7pmyBcha65mL7A+yItWJS8OaqFHxLtKP+PFcCu+5
Q4a5CjK0zvjQHG4U/QPuji3uMVVjNgaZxQhXuBWw9Z2n/FcbNbqrX9cbtmXdPAzM
loorKxnJATVIK3hFwJzmIsjuTqJUs3tXwhIAe/BEosFqCm+niovv2AEyhWfC4Obw
0KoIxj/rbIL9Itai9av8rXpG7jFnwmjQzZafl1LfL9jGqw3c0h8uV3PsEDl/ndxk
xYF6PcUuap+fY2vkTQgoOWbnYeGTuy4RslekhCSVs0jv7IN/aotWXWVHJZ8Y2nZF
Z4KT4J9pLxJ3/EcPFwO5qa1q/TmhorUr7bEiiS6kOroHEuusH6UaBUdb1s3hm8Zh
UcTk+z7ELkqLehMtGQDzU+1uPC3yH46t7tBqPsSzr0HzwEY10qumblTikwhEa1WL
dCkwMF+wMpbuD62QNdzTLAMtuISOVsY38SlWEmnu6TQCK0J9imu64CbAZJVaYQxJ
Xq7XiyfoVXH3t9xeeziPbrTLhrRrFd+9kRP9cPyRZnXklyAgRs4=
=hWuF
-----END PGP SIGNATURE-----


L
L
Ludovic Courtès wrote on 4 Aug 2017 23:54
(address . 27862@debbugs.gnu.org)
87y3qzov6p.fsf@gnu.org
ng0 <ng0@infotropique.org> skribis:

Toggle quote (15 lines)
> Ludovic Courtès transcribed 0.4K bytes:
>> ng0 <ng0@infotropique.org> skribis:
>>
>> > Right now the tor-hidden-service only supports IPv4 naming scheme,
>> > while it is possible to define IPv6 for tor aswell.
>>
>> ‘tor-hidden-service’ does not interpret addresses. So one could write,
>> say:
>>
>> (80 . "[::1]:80")
>
> Oh. Okay, I did not even try it because I live on the dark side of IPv6 ;)
> Then all which needs to be done is a small extension of the documentation
> of tor-hidden-service.

Patch welcome. :-)

Ludo’.
L
L
Ludovic Courtès wrote on 20 Oct 2017 18:03
(address . 27862@debbugs.gnu.org)
874lqtvmao.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) skribis:

Toggle quote (19 lines)
> ng0 <ng0@infotropique.org> skribis:
>
>> Ludovic Courtès transcribed 0.4K bytes:
>>> ng0 <ng0@infotropique.org> skribis:
>>>
>>> > Right now the tor-hidden-service only supports IPv4 naming scheme,
>>> > while it is possible to define IPv6 for tor aswell.
>>>
>>> ‘tor-hidden-service’ does not interpret addresses. So one could write,
>>> say:
>>>
>>> (80 . "[::1]:80")
>>
>> Oh. Okay, I did not even try it because I live on the dark side of IPv6 ;)
>> Then all which needs to be done is a small extension of the documentation
>> of tor-hidden-service.
>
> Patch welcome. :-)

I’m still interested in the doc patch :-), but I’m closing the bug
because it was not an actual bug, AIUI.

Ludo’.
L
L
Ludovic Courtès wrote on 20 Oct 2017 18:03
control message for bug #27862
(address . control@debbugs.gnu.org)
87376dvmak.fsf@gnu.org
tags 27862 notabug
close 27862
?
Your comment

This issue is archived.

To comment on this conversation send an email to 27862@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 27862
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch