Opened 10 years ago

Closed 9 years ago

Last modified 7 years ago

#1369 closed defect (invalid)

ExcludeNodes isn't document as being broken.

Reported by: katmagic Owned by:
Priority: Low Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version: 0.2.2.11-alpha
Severity: Keywords:
Cc: katmagic, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by Sebastian)

ExcludeNodes and ExcludeExitNodes aren't documented as being broken. http://tor.pastebin.com/w3DTwdzi

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (5)

comment:1 Changed 10 years ago by nickm

I'm fine with clarifying the documentation, but just saying "X is somewhat broken" is not enough. Can we
do a patch to say _how_ they're broken?

comment:2 Changed 10 years ago by Sebastian

Yup, I think such a patch is useful, if we don't get this fixed until 0.2.2.x-rc. Also logging a warn seems excessive

comment:3 Changed 10 years ago by nickm

Milestone: Tor: 0.2.2.x-final

comment:4 Changed 9 years ago by Sebastian

Description: modified (diff)
Resolution: Noneinvalid
Status: newclosed

Closing this as invalid, because we're actually getting #1090 implemented and described in the manpage for 0.2.2.x.

comment:5 Changed 7 years ago by nickm

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