Re: [tor-bugs] #24350 [Core Tor/Tor]: A fresh compiled tor does not honor MaxCircuitDirtiness

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#24350: A fresh compiled tor does not honor MaxCircuitDirtiness
--------------------------+------------------------------------
 Reporter:  Zakhar        |          Owner:  (none)
     Type:  defect        |         Status:  assigned
 Priority:  Medium        |      Milestone:  Tor: 0.3.3.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:  tor-client    |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------
Changes (by teor):

 * keywords:  docs => tor-client
 * priority:  Low => Medium
 * type:  enhancement => defect
 * severity:  Minor => Normal
 * milestone:   => Tor: 0.3.3.x-final


Comment:

 It looks like this might be a bug in the new 0.3.x guard code.

 Is there some reason that our circuits change every 5 minutes?
 Do we build a new circuit every 5 minutes?
 Do new streams go on new circuits in 0.3.1, but old circuits in earlier
 versions?

 Replying to [comment:8 Zakhar]:
 > '''[(Almost) Solved]'''
 >
 > I make this a '''low priority documentation enhancement'''!
 >
 > The README says that we must do
 >
 > {{{
 > To build Tor from source:
 >         ./configure && make && make install
 > }}}
 >
 > Proposition:
 > {{{
 > To build Tor from source:
 >         ./configure && make && make install
 >
 >    (or use the build procedure specific to your distribution)
 > }}}
 >
 >
 > Indeed, the documentation could also hint other specific ways of
 building/compiling according to the distribution. Otherwise the trouble is
 that with Debian/Ubuntu '''it works''' but in the end you get an
 executable with strange behavior like the one above.
 >
 >
 > For those who might search, here is how to make it work instead of
 ./configure && make:
 >
 > {{{
 > apt-get install build-essentials fakeroot dpkg-dev
 > apt-get build-dep tor
 > fakeroot debian/rules binary
 > }}}
 >
 > In the end you get a .deb repackaged with your newly compiled source.
 > - same size as the Ubuntu stock binary
 > - same default config files
 > - works with MaxCircuitDirtiness
 >
 >
 > Interesting link: https://www.cyberciti.biz/faq/rebuilding-ubuntu-
 debian-linux-binary-package/
 >
 >
 > '''(Almost)''' because I am now wondering how I will get a working
 Debian Package when I'll try the 0.3.1.8 (or more recent) from the tor
 git/tar.gz
 >
 > Also a small signature issue since I don't have the private key of the
 initial Debian/Ubuntu maintainer, I can't obviously re-sign the package...
 but that is non tor related!

 Please open a separate ticket for this issue.
 We lose track of issues when there is more than one issue in a ticket.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24350#comment:12>
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