aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2010-10-04Add public_server_mode function.Robert Ransom
2010-10-04Correct a bogus comment.Robert Ransom
Whether or not OpenSSL reference-counts SSL_CTX objects is irrelevant; what matters is that Tor reference-counts its wrapper objects for SSL_CTXs.
2010-10-04Correct a couple of log messages in tortls.cRobert Ransom
2010-10-04Fix several comments in tortls.cRobert Ransom
2010-10-04Clarify PublishServerDescriptor even moreNick Mathewson
2010-10-04Merge remote branch 'rransom/manpage-fixes' into maint-0.2.2Nick Mathewson
2010-10-04Merge remote branch 'origin/maint-0.2.1' into maint-0.2.2Nick Mathewson
2010-10-04Update to the October 1 2010 Maxmind GeoLite Country database.Karsten Loesing
2010-10-01fix commentRoger Dingledine
2010-10-01log when we guess our ip address, not just when we failRoger Dingledine
2010-10-01bump to 0.2.2.17-alpha-devRoger Dingledine
2010-10-01retroactively declare the cbt fixes to be majorRoger Dingledine
also put in release blurbs
2010-09-30Describe BridgeRelay and PublishServerDescriptor more correctly.Robert Ransom
2010-09-30improve rpm init script by borrowing from Debiantor-0.2.2.17-alphaErinn Clark
2010-09-30Update rpm spec file so that it will build without manual intervention on ↵Erinn Clark
all rpm-based distributions
2010-09-30AUTHORS doesn't exist, so stop trying to cp it. Add 'sudo' to a mv that ↵Erinn Clark
needs higher permissions.
2010-09-30bump to 0.2.2.17-alphaRoger Dingledine
2010-09-30write up a changelog fileRoger Dingledine
2010-09-30Add a changes file for the bug1912 fixSebastian Hahn
2010-09-30Note an XXX about potential overflowSebastian Hahn
2010-09-30Use an upper and lower bound for bridge weightsSebastian Hahn
When picking bridges (or other nodes without a consensus entry (and thus no bandwidth weights)) we shouldn't just trust the node's descriptor. So far we believed anything between 0 and 10MB/s, where 0 would mean that a node doesn't get any use from use unless it is our only one, and 10MB/s would be a quite siginficant weight. To make this situation better, we now believe weights in the range from 20kB/s to 100kB/s. This should allow new bridges to get use more quickly, and means that it will be harder for bridges to see almost all our traffic.
2010-09-30Fix check-spacesSebastian Hahn
2010-09-30Merge commit 'mikeperry/bug1772' into maint-0.2.2Roger Dingledine
2010-09-29Nominaly lower the minimum timeout value to 1500.Mike Perry
This won't change any behavior, since it will still be rounded back up to 2seconds, but should reduce the chances of some extra warns.
2010-09-29Merge branch 'bug1772' into maint-0.2.2Roger Dingledine
2010-09-29fix two castsRoger Dingledine
2010-09-29Comment network liveness and change detection behavior.Mike Perry
2010-09-29no measurement circs if not enough build timesRoger Dingledine
In the first 100 circuits, our timeout_ms and close_ms are the same. So we shouldn't transition circuits to purpose CIRCUIT_PURPOSE_C_MEASURE_TIMEOUT, since they will just timeout again next time we check.
2010-09-29refactor and recomment; no actual changesRoger Dingledine
2010-09-29Merge commit 'mikeperry/bug1739' into maint-0.2.2Roger Dingledine
2010-09-29Merge commit 'mikeperry/bug1740' into maint-0.2.2Roger Dingledine
2010-09-29Add changes file.Mike Perry
2010-09-29Cap the circuit build timeout to the max time we've seen.Mike Perry
Also, cap the measurement timeout to 2X the max we've seen.
2010-09-29Do away with the complexity of the network liveness detection.Mike Perry
We really should ignore any timeouts that have *no* network activity for their entire measured lifetime, now that we have the 95th percentile measurement changes. Usually this is up to a minute, even on fast connections.
2010-09-29Fix state checks on liveness handling.Mike Perry
If we really want all this complexity for these stages here, we need to handle it better for people with large timeouts. It should probably go away, though.
2010-09-29Fix non-live condition checks.Mike Perry
Rechecking the timeout condition was foolish, because it is checked on the same codepath. It was also wrong, because we didn't round. Also, the liveness check itself should be <, and not <=, because we only have 1 second resolution.
2010-09-29Add changes file.Mike Perry
2010-09-29Send control port events for timeouts.Mike Perry
We now differentiate between timeouts and cutoffs by the REASON string and the PURPOSE string.
2010-09-29Add changes file.Mike Perry
2010-09-29Only count timeout data for 3 hop circuits.Mike Perry
Use 4/3 of this timeout value for 4 hop circuits, and use half of it for canabalized circuits.
2010-09-28even more commentRoger Dingledine
2010-09-28improve code comments, based on comments from nickRoger Dingledine
2010-09-28a changelog entry for the entrynodes retry messRoger Dingledine
2010-09-28handle ugly edge case in retrying entrynodesRoger Dingledine
Specifically, a circ attempt that we'd launched while the network was down could timeout after we've marked our entrynodes up, marking them back down again. The fix is to annotate as bad the OR conns that were around before we did the retry, so if a circuit that's attached to them times out we don't do anything about it.
2010-09-28Actually notice when our last entrynode goes downRoger Dingledine
Otherwise we'd never set have_minimum_dir_info to false, so the "optimistic retry" would never trigger.
2010-09-28optimistically retry EntryNodes on socks requestRoger Dingledine
We used to mark all our known bridges up when they're all down and we get a new socks request. Now do that when we've set EntryNodes too.
2010-09-28remove a redundant assertRoger Dingledine
2010-09-28refactor; no actual changesRoger Dingledine
2010-09-28Merge branch 'maint-0.2.1' into maint-0.2.2Roger Dingledine
2010-09-28actually retry bridges when your network goes awayRoger Dingledine
7apu2bq3rhoylwmucxizk54afw5jyda7pho4j5zdcqpwkufke7zdzwad.onion