| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
if possible, rather than the elite ones.
svn:r3378
|
| |
|
|
| |
svn:r3377
|
| |
|
|
| |
svn:r3376
|
| |
|
|
|
|
| |
"plausible".
svn:r3375
|
| |
|
|
|
|
| |
autodetect compressed directories and compression itself. (resolves bug 65)
svn:r3374
|
| |
|
|
|
|
| |
connections. "Error: Success!" makes us seem like crazy people."
svn:r3373
|
| |
|
|
|
|
|
|
| |
streams. consolidate the looking into one function so it doesn't
happen again.
svn:r3372
|
| |
|
|
| |
svn:r3371
|
| |
|
|
|
|
|
|
|
| |
a general circ, and called rend_client_rendcirc_has_opened(), which
called connection_ap_attach_pending(), which was needing a rendezvous
circ, so it cannibalized a general circuit, and called ...
svn:r3370
|
| |
|
|
| |
svn:r3369
|
| |
|
|
| |
svn:r3368
|
| |
|
|
| |
svn:r3367
|
| |
|
|
| |
svn:r3366
|
| |
|
|
|
|
|
| |
have fine defaults that you can leave alone in normal operation.
svn:r3365
|
| |
|
|
| |
svn:r3364
|
| |
|
|
|
|
|
| |
first will be helpful.
svn:r3363
|
| |
|
|
| |
svn:r3361
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to the exit policy of the last hop. Intro and rendezvous circs must
be internal circs, to avoid leaking information. Resolve and connect
streams can use internal circs if they want.
New circuit pooling algorithm: make sure to have enough circs around
to satisfy any predicted ports, and also make sure to have 2 internal
circs around if we've required internal circs lately (with high uptime
if we've seen that lately).
Split NewCircuitPeriod config option into NewCircuitPeriod (30 secs),
which describes how often we retry making new circuits if current ones
are dirty, and MaxCircuitDirtiness (10 mins), which describes how long
we're willing to make use of an already-dirty circuit.
Once rendezvous circuits are established, keep using the same circuit as
long as you attach a new stream to it at least every 10 minutes. (So web
browsing doesn't require you to build new rend circs every 30 seconds.)
Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
circ as necessary, if there are any completed ones lying around when
we try to launch one.
Re-instate the ifdef's to use version-0 style introduce cells, since
there was yet another bug in handling version-1 style. We'll try switching
over again after 0.0.9 is obsolete.
Bugfix: when choosing an exit node for a new non-internal circ, don't take
into account whether it'll be useful for any pending x.onion addresses --
it won't.
Bugfix: we weren't actually publishing the hidden service descriptor when
it became dirty. So we only published it every 20 minutes or so, which
means when you first start your Tor, the hidden service will seem broken.
svn:r3360
|
| |
|
|
|
|
|
|
| |
as a third class of worker process), so we can stop shipping with the
beast that is Privoxy.
svn:r3359
|
| |
|
|
| |
svn:r3358
|
| |
|
|
| |
svn:r3357
|
| |
|
|
|
|
|
|
| |
since if you hibernate daily a published uptime of >1day
will be misleading.
svn:r3356
|
| |
|
|
|
|
|
| |
provides good uptime if any virtual_port of the service wants that.
svn:r3355
|
| |
|
|
|
|
| |
start_daemon earlier. This should fix using libevent with RunAsDaemon.
svn:r3354
|
| |
|
|
| |
svn:r3353
|
| |
|
|
| |
svn:r3352
|
| |
|
|
| |
svn:r3351
|
| |
|
|
| |
svn:r3350
|
| |
|
|
|
|
|
| |
consider it handled if there's a circ that fits but isn't high-uptime.
svn:r3349
|
| |
|
|
| |
svn:r3348
|
| |
|
|
| |
svn:r3347
|
| |
|
|
| |
svn:r3346
|
| |
|
|
| |
svn:r3345
|
| |
|
|
| |
svn:r3344
|
| |
|
|
| |
svn:r3343
|
| |
|
|
| |
svn:r3342
|
| |
|
|
|
|
|
|
|
|
|
|
| |
poll-but-sometimes-select mess. This will let us use faster async cores
(like epoll, kpoll, and /dev/poll), and hopefully work better on Windows
too.
There are some fairly nasty changes to main.c here; this will almost
certainly break something. But hey, that's what alphas are for.
svn:r3341
|
| |
|
|
| |
svn:r3340
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
high capacity nodes. When building circuits, choose appropriate nodes.
New config option LongLivedPorts to indicate application streams
that will want high uptime circuits.
When attaching a stream to a circuit, pay attention to its requirements.
This means that every single node in an intro rend circuit, not just
the last one, will have a minimum uptime.
Boost the min uptime from an hour to 24 hours.
svn:r3339
|
| |
|
|
|
|
|
| |
themselves
svn:r3338
|
| |
|
|
|
|
|
| |
clock, don't make his published uptime be a year.
svn:r3337
|
| |
|
|
|
|
|
|
| |
server. only give up hope on network reachability when no other servers
are reachable either.
svn:r3335
|
| |
|
|
|
|
|
| |
nick, do you think this does it? if so, we should maybe backport too.
svn:r3334
|
| |
|
|
|
|
|
|
|
| |
now we reset uptime when a dir fetch entirely fails. this
hopefully has something to do with stability of being on the
network.
svn:r3333
|
| |
|
|
| |
svn:r3331
|
| |
|
|
|
|
|
|
| |
refer in logs to the destination address, not the address of the
application connection.
svn:r3330
|
| |
|
|
| |
svn:r3329
|
| |
|
|
| |
svn:r3328
|
| |
|
|
|
|
|
|
|
|
|
|
| |
tried they were all unreachable, assume we are not connected to
the network.
when an application request comes in during this state, be
optimistic and assume we just reconnected. fetch a new directory
and if it works, begin making circuits.
svn:r3327
|
| |
|
|
| |
svn:r3326
|