| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
| |
This way, as soon was we have a networkstatus, we can ask a cache to give us routers, rather than needing to ask the directories.
svn:r5586
|
| |
|
|
|
|
| |
to padding warnings, moving fields around, and acknowledging that we have no files with over 64 kilolines.
svn:r5583
|
| |
|
|
|
|
| |
intended.
svn:r5582
|
| |
|
|
|
|
| |
publishe network-status.
svn:r5574
|
| |
|
|
|
|
|
| |
what to expect.
svn:r5538
|
| |
|
|
|
|
| |
into a separate function in crypto.c
svn:r5530
|
| |
|
|
| |
svn:r5524
|
| |
|
|
|
|
| |
descriptors that they know they will reject.
svn:r5514
|
| |
|
|
| |
svn:r5511
|
| |
|
|
|
|
| |
shutdown.
svn:r5509
|
| |
|
|
|
|
| |
circuits wanted us to open a given OR connection.
svn:r5489
|
| |
|
|
| |
svn:r5472
|
| |
|
|
|
|
| |
likely to be used.
svn:r5471
|
| |
|
|
|
|
| |
Make it use a hashtable instead of a linear search.
svn:r5469
|
| |
|
|
| |
svn:r5461
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Weasel says circuit_get_by_conn is his main timesink. Most of its
users were just checking whether OR conns had circuits, so add a
circuit count to OR conns, and check that. One was
circuit_about_to_close_conn, which was doing an O(n^2) series of calls
to get all circs on an OR conn, so make an O(n) function for that.
Finally, circuit_get_by_edge_conn was using it as a sanity test that
has been around for a while but never found any actualy insanity, so
kill that.
circuit_get_by_conn is finally dead, which is good, since it was never
sane to begin with.
svn:r5460
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
separately. It's important to keep them separate because internal
circuits have their last hops picked like middle hops, rather than like
exit hops. So exiting on them will break the user's expectations.
- Stop cannibalizing internal circuits for general exits, and stop
cannibalizing exit circuits for rendezvous stuff.
- Don't let new exit streams attach to internal circuits.
- When deciding if we have enough circuits for internal and for exit,
don't count the wrong ones.
- Treat predicted resolves as predicted port 80 exits.
svn:r5457
|
| |
|
|
| |
svn:r5443
|
| |
|
|
|
|
| |
tracking this right. Somebody should valgrind a dirserver on an example net. There should be code to dump this value.
svn:r5442
|
| |
|
|
|
|
|
|
| |
server descriptors that were uploaded to a router in its role as authoritative
dirserver.
svn:r5436
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- If we can't get to a dirserver directly, try going via Tor.
- Don't ever try to connect (as a client) to a place our firewall
options forbid.
- If we specify a proxy and also firewall options, obey the firewall
options even when we're using the proxy: some proxies can only proxy
to certain destinations.
svn:r5431
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
don't tell you (it happens!); and rotate TLS connections once a week.
1) If an OR conn becomes more than a week old, make it obsolete.
2) If it's obsolete and empty, kill it.
3) When an OR makes a second connection to you, allow it.
4) If we want to send a new create cell, but the best conn we've
got is obsolete, and the router is 0.1.1.9-alpha-cvs or later, ask
for a new conn instead.
5) When we time out on circuit building on the first hop, make that
connection obsolete.
svn:r5429
|
| |
|
|
|
|
|
|
|
|
| |
just add the default ones directly to the trusted dirserver list.
This fixes a bug where people running controllers would setconf or
the equivalent, and Tor would start yelling at them about setting
their own DirServer lines.
svn:r5418
|
| |
|
|
| |
svn:r5403
|
| |
|
|
|
|
|
|
|
| |
applications are using socks4, socks4a, socks5-with-ip, or
socks5-with-hostname. This way they don't have to keep mucking
with tcpdump and wondering if something got cached somewhere.
svn:r5399
|
| |
|
|
|
|
|
|
| |
node in mind, we weren't checking to see if that exit node
was already present earlier in the circuit. oops.
svn:r5357
|
| |
|
|
|
|
| |
superseded router descriptor. Roll the signed descriptor info and identifying info into a cache_info struct, and use only that for old_routers.
svn:r5349
|
| |
|
|
| |
svn:r5345
|
| |
|
|
|
|
|
|
| |
125000 circuit_t's after it had been up for a few weeks, which translates
to 20+ megs of wasted space.
svn:r5333
|
| |
|
|
|
|
|
|
| |
be more fair on loaded Tor servers, and it might resolve our
Windows crash bug. It might also slow things down.
svn:r5332
|
| |
|
|
|
|
| |
old ones is definitely some textbook C problem.
svn:r5323
|
| |
|
|
| |
svn:r5317
|
| |
|
|
|
|
| |
domain. Domains are now bitmasks... just in case. Make some err msgs non-general.
svn:r5309
|
| |
|
|
|
|
| |
new logging
svn:r5301
|
| |
|
|
| |
svn:r5285
|
| |
|
|
|
|
| |
of identifiers. src/or has not been converted yet. Domains dont do anything yet.
svn:r5284
|
| |
|
|
| |
svn:r5279
|
| |
|
|
|
|
| |
change its interface; add modifier functions to add/remove elements from the current routerlist (so we can add indices).
svn:r5276
|
| |
|
|
|
|
| |
of a generic "Servers unavailable."
svn:r5274
|
| |
|
|
|
|
|
| |
since none of our users know what it means to bind an address or port.
svn:r5260
|
| |
|
|
| |
svn:r5253
|
| |
|
|
| |
svn:r5251
|
| |
|
|
| |
svn:r5250
|
| |
|
|
|
|
| |
responses. (when DIR_PURPOSE_FETCH_ROUTERDESC)
svn:r5249
|
| |
|
|
|
|
| |
server descriptor, but not too often
svn:r5246
|
| |
|
|
| |
svn:r5238
|
| |
|
|
|
|
| |
client can handle extra labeled info in its events. Add moreinfo to the "what is ready for downloading" msg so we can investigate digest-related download rules
svn:r5237
|
| |
|
|
| |
svn:r5217
|
| |
|
|
| |
svn:r5208
|
| |
|
|
| |
svn:r5204
|