Tor 0.1.0.17: новая стабильная версия
Tor 0.1.0.17 fixes a crash bug for servers that enable hibernation,
lets Windows servers scale better, and tries to reduce the bandwidth
overhead from the old-style directory protocol. Both clients and servers
are encouraged to upgrade.
http://tor.eff.org/download
Changes in version 0.1.0.17 – 2006-02-17
o Crash bugfixes on 0.1.0.x:
- When servers with a non-zero DirPort came out of hibernation,
sometimes they would trigger an assert.
o Other important bugfixes:
- On platforms that don't have getrlimit (like Windows), we were
artificially constraining ourselves to a max of 1024
connections. Now just assume that we can handle as many as 15000
connections. Hopefully this won't cause other problems.
o Backported features:
- When we're a server, a client asks for an old-style directory,
and our write bucket is empty, don't give it to him. This way
small servers can continue to serve the directory *sometimes*,
without getting overloaded.
- Whenever you get a 503 in response to a directory fetch, try
once more. This will become important once servers start sending
503's whenever they feel busy.
- Fetch a new directory every 120 minutes, not every 40 minutes.
Now that we have hundreds of thousands of users running the old
directory algorithm, it's starting to hurt a lot.
- Bump up the period for forcing a hidden service descriptor upload
from 20 minutes to 1 hour.
Обновилась нестабильная версия (CVS) до 0.1.1.14 alpha.
Changes in version 0.1.1.14-alpha – 2006-02-20
- Don't die if we ask for a stdout or stderr log (even implicitly)
and we're set to RunAsDaemon — just warn.
- We still had a few bugs in the OR connection rotation code that
caused directory servers to slowly aggregate connections to other
- Make log entries on Win32 include the name of the function again.
- We were treating a pair of exit policies if they were equal even
if one said accept and the other said reject — causing us to
- Retry pending server downloads as well as pending networkstatus
downloads when we unexpectedly get a socks request.
- We were ignoring the IS_FAST flag in the directory status,
meaning we were willing to pick trivial-bandwidth nodes for "fast"
- If the controller's SAVECONF command fails (e.g. due to file
permissions), let it know that it failed.
o Features:fast Tor servers. This time for sure!
not always publish a new descriptor since we thought nothing
had changed.
connections.
small servers can continue to serve the directory *sometimes*,
without getting overloaded.
makes sense.
and OR conns to port 443.
target arch.
info and hidserv info or let the controller do it, and
PublishServerDescriptor and PublishHidServDescriptors.
Tor (it assumes your controller bootstraps your circuits).