Opened 5 years ago

Closed 3 years ago

#12163 closed defect (worksforme)

Tor 0.2.4.22 doesn't bind to low IPv6 ports

Reported by: rommelbak Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.4.22
Severity: Normal Keywords: IPv6, tor-03-unspecified-201612
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

IPv4 works fine with a low port number (445 in my case), but IPv6 doesn't.

Config:

ORPort 445
ORPort [2001:db8:a:b::c]:445

[warn] Could not bind to 2001:db8:a:b::c:445:
| > | Permission denied

Now when I change the IPv6 port to a higher number everything works fine:

ORPort [2001:db8:a:b::c]:4445

OS is Ubuntu; Linux version 3.13.0-24-generic (buildd@batsu) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014

Child Tickets

Change History (7)

comment:1 Changed 5 years ago by nickm

Status: newneeds_information

Hm. What is giving Tor process permission to bind to IPv4 port 445 ? Are you starting as root, or running with elevated capabilities, or something else?

comment:2 Changed 5 years ago by nickm

Milestone: Tor: 0.2.6.x-final

comment:3 Changed 5 years ago by massar

Unless one does non-root without giving the right capability, this just works(tm).

As an example:
https://atlas.torproject.org/#details/BDB26EF60A419089CA3AA0891AF1681455285D48

OR Addresses
216.66.85.146:443,[2001:470:1:1e4::2]:443

comment:4 Changed 5 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.???

comment:5 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:6 Changed 3 years ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:7 Changed 3 years ago by nickm

Resolution: worksforme
Severity: Normal
Status: needs_informationclosed
Note: See TracTickets for help on using tickets.