Opened 14 years ago

Last modified 7 years ago

#156 closed defect (Fixed)

"NoPublish 1" honored incompletely

Reported by: rm Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version: 0.1.0.8-rc
Severity: Keywords:
Cc: rm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When I set

ClientOnly 1
NoPublish 1

in my torrc, the server nonetheless reports


Jun 09 22:33:32.750 [notice] Tor has successfully opened a circuit. Looks like it's working.
Jun 09 22:33:32.750 [notice] Now checking whether ORPort and DirPort are reachable... (this may take several minutes)
Jun 09 22:33:43.000 [notice] directory_handle_command_get(): Client asked for the mirrored directory, but we don't have a good one yet. Sending 503 Dir not available.
Jun 09 22:34:36.500 [notice] router_orport_found_reachable(): Your ORPort is reachable from the outside. Excellent. Publishing server descriptor.


However, the node is not listed in the directory, so this seems to be ok. The two ports are actually probed from the outside, though.

Tested on Win2000, SP4.

[Automatically added by flyspray2trac: Operating System: Windows 2k/XP]

Child Tickets

Change History (2)

comment:1 Changed 14 years ago by phobos

flyspray2trac: bug closed.
This was fixed in 0.1.0.9.

comment:2 Changed 7 years ago by nickm

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