[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #25423 [Core Tor/Stem]: Treat 'ExitRelay 0' as a reject-all policy
#25423: Treat 'ExitRelay 0' as a reject-all policy
---------------------------+------------------------
Reporter: atagar | Owner: dmr
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: Core Tor/Stem | Version:
Severity: Normal | Resolution: fixed
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: atagar | Sponsor:
---------------------------+------------------------
Comment (by dmr):
[comment:6 Quoting dmr]:
> ==== 1. Failure for `GETINFO exit-policy/full` to return info.
> [...]
>
> I've noticed two circumstances in which the exit-policy is unqueryable:
> * [...]
> * tor is configured as a client
>
> The former is [...]
> The latter is persistent, i.e. the client-only configuration ALWAYS
returns this:
> {{{
> >>> GETINFO exit-policy/full
> 551 router_get_my_routerinfo returned NULL
> }}}
>
> `Controller.get_exit_policy()` has the `default` parameter. Without
specifying a default, `get_exit_policy()` will raise an exception in these
cases.
Tickets filed; handling these scenarios is covered in:
* #25852 - tor and control spec
* #25853 - stem behavior
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25423#comment:15>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs