Upstream changelog:
Changes in version 0.2.0.31 - 2008-09-03
o Major bugfixes:
- Make sure that two circuits can never exist on the same connection
with the same circuit ID, even if one is marked for close. This
is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
- Rel
debain/changelog:
tor (0.2.0.31-1) unstable; urgency=low
* New upstream version.
* Tweak a few error messages in the init script to use the proper variables
(not that it should matter, the Right One has the same value, but still)
and to list more possible error reasons.
-- Peter Palf
diffstat between 0.1.2 and 0.2.0.31.
** Attachment added: "tor.diffstat"
http://launchpadlibrarian.net/18342956/tor.diffstat
--
[FFe] tor version bump to 0.2.X
https://bugs.launchpad.net/bugs/261693
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
Lenny has version 0.2.0.31-1.
It builds and installs correctly on intrepid, without adaptation to debian
package.
install log:
(intrepid)[EMAIL PROTECTED]:/var/cache/pbuilder/result$ sudo dpkg -i
tor_0.2.0.31-1_i386.deb
(Leyendo la base de datos ...
107308 ficheros y directorios instalados actu
I think the intro to the announcement summarizes it best:
"Tor 0.2.0.30 switches to a more efficient directory distribution design,
adds features to make connections to the Tor network harder to block,
allows Tor to act as a DNS proxy, adds separate rate limiting for relayed
traffic to make it eas
0.2.x offers major fixes, but of course I do not know if they are enough to
push this to Intrepid. Here are some of those fixes that I think might be the
important ones:
- Non-exit relays no longer answer "resolve" relay cells, so they
can't be induced to do arbitrary DNS requests.
As I communicated in IRC earlier today, we are well past Feature Freeze
and bordering on beta freeze. During this phase it's not customary to
import new versions of packages but focus on bugfixing.
Is there anything critically important in this new release that would
affect the Intrepid version in
