[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #1127 [Tor Relay]: no shutdown descriptor published when ORPort is closed but client stays up
#1127: no shutdown descriptor published when ORPort is closed but client stays up
--------------------------------+-------------------------------------------
Reporter: nickm | Type: defect
Status: new | Priority: minor
Milestone: Tor: 0.2.3.x-final | Component: Tor Relay
Version: 0.2.2.5-alpha | Resolution: None
Keywords: | Parent:
--------------------------------+-------------------------------------------
Changes (by nickm):
* milestone: => Tor: 0.2.3.x-final
Old description:
> (Posted by request from Scott Bennett.)
>
> Category: tor router -> tor client
> Operating System: observed on FreeBSD 7.2-STABLE
> Reported Version: 0.2.2.3-alpha
> Title: no shutdown descriptor published when ORPort is closed but client
> stays up
> Reported By: Scott Bennett
>
> Description: When tor is running as both a router and a client, if a
> SIGINT
> is sent to tor, tor closes the ORPort (and DirPort if
> applicable),
> publishes a shutdown descriptor (i.e., a new descriptor in which
> the
> "observed maximum 10s data rate in previous 24 hrs" is set to 0
> to
> discourage further attempts to include the node in new circuits),
> and
> proceeds with the rest of the shutdown procedure. However, given
> the
> same starting conditions, if the ORPort line in torrc is
> commented out
> and a SIGHUP is sent to tor, tor will read the updated torrc,
> notice
> that the ORPort is no longer to be used, close the ORPort (and
> DirPort
> if applicable), and continue operation as a client process
> *without*
> publishing a shutdown procedure. This situation results in many
> unnecessary attempts by clients and routers to connect to the
> ORPort
> (and DirPort if applicable) after it has been closed, wasting
> time and
> causing avoidable circuit construction failures. This was
> observed in
> tor 0.2.2.3-alpha. I haven't yet tried it in 0.2.2.5-alpha.
>
> [Automatically added by flyspray2trac: Operating System: BSD]
New description:
(Posted by request from Scott Bennett.)
Category: tor router -> tor client
Operating System: observed on FreeBSD 7.2-STABLE
Reported Version: 0.2.2.3-alpha
Title: no shutdown descriptor published when ORPort is closed but client
stays up
Reported By: Scott Bennett
Description: When tor is running as both a router and a client, if a
SIGINT
is sent to tor, tor closes the ORPort (and DirPort if applicable),
publishes a shutdown descriptor (i.e., a new descriptor in which
the
"observed maximum 10s data rate in previous 24 hrs" is set to 0 to
discourage further attempts to include the node in new circuits),
and
proceeds with the rest of the shutdown procedure. However, given
the
same starting conditions, if the ORPort line in torrc is commented
out
and a SIGHUP is sent to tor, tor will read the updated torrc,
notice
that the ORPort is no longer to be used, close the ORPort (and
DirPort
if applicable), and continue operation as a client process
*without*
publishing a shutdown procedure. This situation results in many
unnecessary attempts by clients and routers to connect to the
ORPort
(and DirPort if applicable) after it has been closed, wasting time
and
causing avoidable circuit construction failures. This was
observed in
tor 0.2.2.3-alpha. I haven't yet tried it in 0.2.2.5-alpha.
[Automatically added by flyspray2trac: Operating System: BSD]
--
Comment:
If we can fix this in 0.2.3, we should. It would be even nicer to have
this happen as a part of a refactoring of our general "what's our own
state" code, which is a bit of a spaghettiish mess to begin with.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1127#comment:1>
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