#25842 closed defect (duplicate)

'GETINFO exit-policy/full' fails when disconnected

Reported by: atagar Owned by:
Priority: High Milestone: Tor: 0.3.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: fast-fix, tor-control
Cc: dmr Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

On #25423 dmr noticed that 'GETINFO exit-policy/full' fails when tor lacks an address...

ProtocolError: GETINFO response didn't have an OK status:
router_get_my_routerinfo returned NULL

No big whoop, but for this method to be useful I need for it to always tell us what our effective policy is (maybe that's 'reject *:*' when disconnected?). In the meantime Stem is using the following as a workaround...

https://gitweb.torproject.org/stem.git/commit/?id=f61e913

Child Tickets

Change History (5)

comment:1 Changed 12 months ago by dgoulet

Keywords: fast-fix tor-control added
Milestone: Tor: 0.3.4.x-final

comment:2 Changed 12 months ago by dgoulet

So GETINFO fingerprint returns:

551 Not running in server mode

... which is probably what we should do here after discussing this with dmr on IRC.

comment:3 Changed 12 months ago by dmr

Cc: dmr added

comment:4 in reply to:  2 Changed 12 months ago by dmr

Replying to dgoulet:

So GETINFO fingerprint returns:

551 Not running in server mode

... which is probably what we should do here after discussing this with dmr on IRC.

Oops, to place this discussion into context: dgoulet and I discussed this ticket along with behavior for clients, and I caused some miscommunication by bringing up too many things at once. His comment above is related to client behavior.

That is tracked instead in:

comment:5 Changed 11 months ago by dgoulet

Resolution: duplicate
Status: newclosed

Closing this. Duplicate to #25852 that we just merged.

Note: See TracTickets for help on using tickets.