| Commit message (Collapse) | Author | Age |
|
|
|
| |
svn:r260
|
|
|
|
| |
svn:r258
|
|
|
|
| |
svn:r249
|
|
|
|
| |
svn:r240
|
|
|
|
| |
svn:r237
|
|
|
|
| |
svn:r236
|
|
|
|
| |
svn:r235
|
|
|
|
|
|
|
|
| |
now we rebuild the circuit periodically (but only if it's been used),
and we can further abstract it to do incremental circuit building, etc.
svn:r233
|
|
|
|
|
|
| |
setup/teardown
svn:r232
|
|
|
|
| |
svn:r231
|
|
|
|
| |
svn:r230
|
|
|
|
|
|
|
| |
route selection still doesn't pay attention to exit policies though
svn:r227
|
|
|
|
| |
svn:r225
|
|
|
|
|
|
| |
separate file.
svn:r224
|
|
|
|
| |
svn:r218
|
|
|
|
|
|
|
|
| |
if the directory is remade while an OR is handshaking, the directory
needs to become dirty again when the handshake succeeds
svn:r215
|
|
|
|
| |
svn:r208
|
|
|
|
| |
svn:r198
|
|
|
|
|
|
|
|
| |
if your ORPort is non-zero then you must connect to all nodes
if your DirPort is non-zero then you must act like a directory server
svn:r192
|
|
|
|
| |
svn:r187
|
|
|
|
| |
svn:r174
|
|
|
|
| |
svn:r170
|
|
|
|
| |
svn:r166
|
|
|
|
| |
svn:r162
|
|
|
|
| |
svn:r161
|
|
|
|
|
|
|
| |
serious performance increase over non-caching
svn:r158
|
|
|
|
|
|
|
|
|
| |
(they wouldn't have before)
alternate code which bypasses the dns farm, so we can compare speed
svn:r154
|
|
|
|
|
|
|
| |
performance is better, but not by much. not sure why yet.
svn:r153
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
we're closer to an OS X port
CVS: ----------------------------------------------------------------------
svn:r146
|
|
|
|
|
|
|
|
|
|
|
| |
we also queue data cells destined for a circuit that is
pending, and process them once the circuit opens
destroys reach into the queue and remove the pending onion,
along with its collected data cells
svn:r142
|
|
|
|
| |
svn:r140
|
|
|
|
|
|
|
| |
first cut, probably needs more playing with
svn:r137
|
|
|
|
|
|
|
| |
reformat parts of onion.c
svn:r136
|
|
|
|
| |
svn:r132
|
|
|
|
|
|
| |
clean up error handling in onion.c
svn:r131
|
|
|
|
| |
svn:r130
|
|
|
|
|
|
|
|
|
| |
now tor can be run safely inside nat'ed areas that kill idle
connections; and the proxy can handle when you suspend your laptop
and then emerge hours later from a new domain.
svn:r125
|
|
|
|
| |
svn:r123
|
|
|
|
| |
svn:r121
|
|
|
|
|
|
|
|
|
|
| |
prkey is only fetched when it's needed
tor nodes who aren't dirservers now fetch directories and autoconnect
to new nodes listed in the directory
default role is a non-dirserver node
svn:r120
|
|
|
|
|
|
|
| |
if connecting to a dirserver fails, remove it from the router array
svn:r113
|
|
|
|
|
|
|
|
| |
proxies now periodically pull down an hourly-updated directory,
and replace their router list with it if it parses correctly.
svn:r112
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
revamped the router reading section
reference counting for crypto pk env's (so we can dup them)
we now read and write pem pk keys from string rather than from FILE*,
in anticipation of fetching directories over a socket
(so now on startup we slurp in the whole file, then parse it as a string)
fixed a bug in the proxy side, where you could get some circuits
wedged if they showed up while the connection was being made
svn:r110
|
|
|
|
| |
svn:r108
|
|
|
|
|
|
|
|
|
|
|
| |
httpap is obsolete; we support privoxy directly now!
smtpap is obsolete; need to find a good socks4a-enabled smtp proxy/client
I dub thee 0.0.1.
svn:r107
|
|
|
|
| |
svn:r106
|
|
|
|
| |
svn:r104
|
|
|
|
|
|
|
| |
see http://archives.seul.org/or/dev/Sep-2002/msg00018.html
svn:r103
|