Opened 11 years ago

Last modified 11 years ago

#914 closed defect (Not a bug)

When the clock jumps, Tor will trigger CIRCUIT_ESTABLISHED

Reported by: sjmurdoch Owned by: sjmurdoch
Priority: Low Milestone:
Component: Applications/Tor bundles/installation Version: 0.2.1.10-alpha
Severity: Keywords:
Cc: sjmurdoch, arma, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

When Tor detects that the clock has jumped, it will destroy
existing circuits and create new ones (or/circuitbuild.c:737).

Once Tor has created new circuits, it will trigger the same
events as would happen if Tor had established its first
circuit, including sending the CIRCUIT_ESTABLISHED control event
and BOOTSTRAP_STATUS_DONE bootstrap event (or/circuitbuild.c:682)

Vidalia/Tor Browser Bundle uses CIRCUIT_ESTABLISHED to launch Firefox
and Pidgin. So when this scenario occurs, there will the two
instances running. This would be confusing to users.

I'm not sure whether this is best fixed in Vidalia or Tor.

The specification on CIRCUIT_ESTABLISHED is not very clear on
whether it should be generated multiple times.

"Tor is able to establish circuits for client use. This event will

only be sent if we just built a circuit that changed our mind --
that is, prior to this event we didn't know whether we could
establish circuits."

Proposal 137 indicates that currently Tor does not send BOOTSTRAP_STATUS_DONE
more than once (although "monotonically" could be interpreted as
monotonically non-decreasing rather than monotonically increasing.

"Current Tor versions enter these phases in order, monotonically;

future Tors MAY revisit earlier stages."

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (5)

comment:1 Changed 11 years ago by arma

Seems to me that Vidalia should remember whether it's done something
that it doesn't want to do more than once, and then not do it more than
once.

comment:2 Changed 11 years ago by arma

(The multiple circuit-established events is actually intentional behavior.
Once your clock jumps, and we're not sure whether your network is working,
then we try to use it. If we find that it is working, then you'll want to
hear about it.)

comment:3 Changed 11 years ago by arma

edmanm> arma: yeah, i saw steven mention that a bit ago. i think the right
thing to do would be to fix the browser launching stuff in vidalia to
remember that it already launched the browser.

comment:4 Changed 11 years ago by nickm

So, close this as not-a-bug? Any objections?

comment:5 Changed 11 years ago by sjmurdoch

flyspray2trac: bug closed.
Moved to a Vidalia bug report:
http://trac.vidalia-project.net/ticket/467

Note: See TracTickets for help on using tickets.