Opened 4 years ago

Closed 4 years ago

#12670 closed enhancement (fixed)

HiddenServicePort TARGET IPv6 address

Reported by: grarpamp Owned by:
Priority: Medium Milestone: Tor: 0.2.6.x-final
Component: Core Tor/Tor Version: Tor: 0.2.4.22
Severity: Keywords: tor-hs documentation easy 026-triaged-1
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The man page HiddenServicePort does not say anything about TARGET being an IPv6 address. Since Tor is becoming IPv6 enabled it probably should (ie: ::1, and precedence). There are some combinations to consider supporting if not already done (latter dependant on host if tor is not bound to both)...

4 -> TARGET 4
6 -> TARGET 6

4 -> TARGET 6
6 -> TARGET 4

Child Tickets

Change History (4)

comment:1 Changed 4 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.6.x-final

comment:2 Changed 4 years ago by nickm

Keywords: tor-hs documentation easy 026-triaged-1 added

AFAIK,

hiddenserviceport 80 [::1]:80

works fine. I think this is just a documentation patch.

comment:3 Changed 4 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.7.x-final

comment:4 Changed 4 years ago by nickm

Milestone: Tor: 0.2.7.x-finalTor: 0.2.6.x-final
Resolution: fixed
Status: newclosed

Actually wait; that's a documentation bug. Added one-liner doc fix as ab08d8c4f7a4a6120756e964a086219a1dc3aaa2

Note: See TracTickets for help on using tickets.