| Age | Commit message (Collapse) | Author |
|---|
|
svn:r2652
|
|
still need to track bandwidth, and make decisions based on bandwidth
svn:r2630
|
|
tor-resolve can be smaller.
svn:r2629
|
|
svn:r2326
|
|
* \file circuitbuild.c
* \brief The actual details of building circuits.
* \file circuitlist.c
* \brief Manage the global circuit list.
* \file circuituse.c
* \brief Launch the right sort of circuits, attach streams to them.
* \file connection_edge.c
* \brief Handle edge streams.
* \file onion.c
* \brief Functions to queue create cells, and handle onionskin
* parsing and creation.
* \file relay.c
* \brief Handle relay cell encryption/decryption, plus packaging and
* receiving from circuits.
svn:r1863
|
|
svn:r1854
|
|
routerlist.c
svn:r1846
|
|
connection_ap_handshake_attach_circuit attaches to a circ of the
right purpose
add a skeletal rendclient.c
svn:r1441
|
|
svn:r1429
|
|
and service IDs, and store/load them from disk
svn:r1410
|
|
svn:r1403
|
|
successful/failed connections, successful/failed extends, and
connection uptimes.
It's still not done: more tests are needed, and not everything calls
connection/circuit_mark_for_close properly. This skews the results.
Also, there needs to be a 'testing' mode for non-OP ORs, where they
periodically build circuits just to test whether extends work.
svn:r1313
|
|
or tested yet.
svn:r1310
|
|
svn:r1119
|
|
svn:r1082
|
|
and routerlist.c for handling routerlist.
svn:r887
|
|
svn:r503
|
|
svn:r478
|
|
svn:r451
|
|
please poke at it and report bugs
still needs polishing, and only handles onions now (should handle
OR handshakes too)
svn:r402
|
|
it wasn't working, and it was harder than we'd anticipated
not worth it.
svn:r316
|
|
svn:r298
|
|
svn:r247
|
|
svn:r230
|
|
separate file.
svn:r224
|
|
svn:r197
|
|
svn:r183
|
|
on startup, it forks off a master dns handler, which forks off dns
slaves (like the apache model). slaves as spawned as load increases,
and then reused. excess slaves are not ever killed, currently.
implemented topics. each topic has a receive window in each direction
at each edge of the circuit, and sends sendme's at the data level, as
per before. each circuit also has receive windows in each direction at
each hop; an edge sends a circuit-level sendme as soon as enough data
cells have arrived (regardless of whether the data cells were flushed
to the exit conns). removed the 'connected' cell type, since it's now
a topic command within data cells.
at the edge of the circuit, there can be multiple connections associated
with a single circuit. you find them via the linked list conn->next_topic.
currently each new ap connection starts its own circuit, so we ought
to see comparable performance to what we had before. but that's only
because i haven't written the code to reattach to old circuits. please
try to break it as-is, and then i'll make it reuse the same circuit and
we'll try to break that.
svn:r152
|
|
when we had lots of new onions coming in, we were using 40% of
our time searching through the tracked_onions linked list.
svn:r150
|
|
svn:r133
|
|
proxies now periodically pull down an hourly-updated directory,
and replace their router list with it if it parses correctly.
svn:r112
|
|
the package is tor, the binary is or.
and i added our project plan to the todo file.
svn:r93
|
|
svn:r92
|
|
svn:r49
|
|
svn:r31
|
|
The 'or' process can now be told (by the global_role variable) what
roles this server should play -- connect to all ORs, listen for ORs,
listen for OPs, listen for APs, or any combination.
* everything in /src/op/ is now obsolete.
* connection_ap.c now handles all interactions with application proxies
* "port" is now or_port, op_port, ap_port. But routers are still always
referenced (say, in conn_get_by_addr_port()) by addr / or_port. We
should make routers.c actually read these new ports (currently I've
kludged it so op_port = or_port+10, ap_port=or_port+20)
* circuits currently know if they're at the beginning of the path because
circ->cpath is set. They use this instead for crypts (both ways),
if it's set.
* I still obey the "send a 0 back to the AP when you're ready" protocol,
but I think we should phase it out. I can simply not read from the AP
socket until I'm ready.
I need to do a lot of cleanup work here, but the code appears to work, so
now's a good time for a checkin.
svn:r22
|
|
general cleanup, particularly in buffers.c
svn:r17
|
|
autoheader && automake" from the top dir.
svn:r10
|
