Opened 11 years ago

Last modified 7 years ago

#579 closed defect (Fixed)

Failed to parse/validate config: Configs without ports should be valid

Reported by: xiando Owned by:
Priority: Very High Milestone:
Component: Core Tor/Tor Version: 0.2.0.9-alpha
Severity: Keywords:
Cc: xiando, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Tor story regarding a configuration I tried is:

"Failed to parse/validate config: SocksPort, TransPort, NatdPort, and ORPort are all undefined? Quitting."

If I - in theory - were to define

HiddenServiceDir
HiddenServicePort

then I would not, if that was indeed the case, require or desire to have anything at all
to do with SocksPort, TransPort, NatdPort, and ORPort.

Tor just atleast start (maby just give a warning? or nothing?) if involvement with
HiddenServiceDir / HiddenServicePort is indicated.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (3)

comment:1 Changed 11 years ago by nickm

resolved in r13036.

comment:2 Changed 11 years ago by nickm

flyspray2trac: bug closed.

comment:3 Changed 7 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.