| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
svn:r333
|
| |
|
|
|
|
|
| |
clean up circuit_deliver_relay_cell convention
svn:r312
|
| |
|
|
|
|
|
| |
point to the streams for this circ.
svn:r296
|
| |
|
|
|
|
|
|
|
|
| |
remove sendme cells
replace malloc with tor_malloc
patch (but not track down) bug in onion pending list
streamline connection_ap handshake
svn:r293
|
| |
|
|
|
|
|
|
| |
the OP only crypts the appropriate number of times depending on which
layer (hop on the path) it's for/from.
svn:r262
|
| |
|
|
| |
svn:r260
|
| |
|
|
| |
svn:r258
|
| |
|
|
| |
svn:r253
|
| |
|
|
| |
svn:r249
|
| |
|
|
| |
svn:r248
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
svn:r230
|
| |
|
|
|
|
| |
separate file.
svn:r224
|
| |
|
|
|
|
|
| |
(breaks backward compatibility)
svn:r222
|
| |
|
|
| |
svn:r206
|
| |
|
|
| |
svn:r204
|
| |
|
|
| |
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:r176
|
| |
|
|
| |
svn:r161
|
| |
|
|
|
|
|
|
|
| |
(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
|
| |
|
|
|
|
|
| |
don't list non-open ORs in the directory
svn:r134
|
| |
|
|
| |
svn:r132
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
tor can now interface directly with mozilla, as a socks 4 host.
but note that mozilla does the dns resolution itself, so you're leaking
anonymity.
svn:r119
|
| |
|
|
| |
svn:r118
|
| |
|
|
|
|
|
| |
should be more reliable now (?)
svn:r111
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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:r104
|
| |
|
|
|
|
|
| |
see http://archives.seul.org/or/dev/Sep-2002/msg00018.html
svn:r103
|
| |
|
|
|
|
|
| |
(it seemed to work anyway, but...)
svn:r100
|
| |
|
|
| |
svn:r82
|
| |
|
|
|
|
| |
OpenSSL directly.
svn:r76
|
| |
|
|
| |
svn:r71
|
| |
|
|
|
|
|
|
|
|
|
| |
I modified new_route so we don't pick twins back-to-back in the path.
I also had to patch my previous uses of connection_twin_get_by_addr_port()
because they assumed that "addr" and "port" would be the same for a twin
as for the original router.
svn:r56
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Servers are allowed to send 100 cells initially, and can't send more until
they receive a 'sendme' cell from that direction, indicating that they
can send 10 more cells. As it currently stands, the exit node quickly
runs out of window, and sends bursts of 10 whenever a sendme cell gets
to him. This is much much much faster (and more flexible) than the old
"give each circuit 1 kB/s and hope nothing overflows" approach.
Also divided out the connection_watch_events into stop_reading,
start_writing, etc. That way we can control them separately.
svn:r54
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each socket reads at most 'bandwidth' bytes per second sustained, but
can handle bursts of up to 10*bandwidth bytes.
Cells are now sent out at evenly-spaced intervals, with padding sent
out otherwise. Set Linkpadding=0 in the rc file to send cells as soon
as they're available (and to never send padding cells).
Added license/copyrights statements at the top of most files.
router->min and router->max have been merged into a single 'bandwidth'
value. We should make the routerinfo_t reflect this (want to do that,
Mat?)
As the bandwidth increases, and we want to stop sleeping more and more
frequently to send a single cell, cpu usage goes up. At 128kB/s we're
pretty much calling poll with a timeout of 1ms or even 0ms. The current
code takes a timeout of 0-9ms and makes it 10ms. prepare_for_poll()
handles everything that should have happened in the past, so as long as
our buffers don't get too full in that 10ms, we're ok.
Speaking of too full, if you run three servers at 100kB/s with -l debug,
it spends too much time printing debugging messages to be able to keep
up with the cells. The outbuf ultimately fills up and it kills that
connection. If you run with -l err, it works fine up through 500kB/s and
probably beyond. Down the road we'll want to teach it to recognize when
an outbuf is getting full, and back off.
svn:r50
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
basically, a twin is a router which is different except it shares
the same keypair. so in cases where we want to find a "next router"
and all we really care is that it can decrypt the next onion layer,
then a twin is just as good.
we still need to decide how to mark twins in the routerinfo_t and in
the routers config file.
svn:r30
|
| |
|
|
| |
svn:r29
|
|
|
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
|