| Commit message (Collapse) | Author | Age |
|
|
|
| |
svn:r6089
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ask for a circuit that Tor won't try to use.
Extend the EXTENDCIRCUIT controller command to let you specify
the purpose if you're starting a new circuit.
Add a new SETCIRCUITPURPOSE controller command to let you
change a circuit's purpose after it's been created.
svn:r6075
|
|
|
|
|
|
|
| |
error string.
svn:r6053
|
|
|
|
|
|
|
| |
whee.
svn:r6003
|
|
|
|
| |
svn:r5949
|
|
|
|
|
|
|
|
|
|
| |
doing address remapping, handling .exit and .onion idioms, and so on.
Now we are more uniform in making sure that the controller hears about
all new connections, and making sure it hears when they close.
svn:r5897
|
|
|
|
|
|
|
| |
include the whitespace/newline/etc in our complaint.
svn:r5841
|
|
|
|
|
|
| |
them lazily on disk.
svn:r5827
|
|
|
|
|
|
|
| |
this is our last easy chance for a wholesale change. heave ho.
svn:r5782
|
|
|
|
|
|
|
| |
closes bug 237.
svn:r5770
|
|
|
|
| |
svn:r5760
|
|
|
|
| |
svn:r5734
|
|
|
|
|
|
|
|
| |
(config options EntryNodes and StrictEntryNodes still not
implemented.)
svn:r5673
|
|
|
|
|
|
| |
intended.
svn:r5582
|
|
|
|
|
|
|
| |
arguments, but then just keep on going anyway.
svn:r5575
|
|
|
|
|
|
|
|
|
|
|
| |
513 Unrecognized option value
it's not unrecognized. it's unacceptable. (in this case, i still
have to consult the logs to figure out why, but at least i have
an inkling that maybe i should.)
svn:r5561
|
|
|
|
|
|
|
|
|
|
|
|
| |
we screwed up the formatting in wild and unpredictable ways.
fix it before it becomes convention to format logs in wild and
unpredictable ways.
still need to do src/common/ someday.
svn:r5551
|
|
|
|
|
|
| |
160-character-per-line limit; this will creep down.
svn:r5548
|
|
|
|
|
|
| |
circuits wanted us to open a given OR connection.
svn:r5489
|
|
|
|
|
|
|
|
| |
server descriptors that were uploaded to a router in its role as authoritative
dirserver.
svn:r5436
|
|
|
|
| |
svn:r5422
|
|
|
|
| |
svn:r5421
|
|
|
|
| |
svn:r5414
|
|
|
|
|
|
|
|
|
|
|
|
| |
any answer at all. this is clearly a bug.
the more interesting bug is whether things like setconf, getconf,
and so on should return 250 OK if you give them no arguments. should
we have a new "you didn't ask me anything" response code, or just
leave it as is?
svn:r5412
|
|
|
|
| |
svn:r5400
|
|
|
|
|
|
| |
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:r5317
|
|
|
|
| |
svn:r5306
|
|
|
|
|
|
| |
interface; use new circ_log_path interface
svn:r5302
|
|
|
|
| |
svn:r5285
|
|
|
|
|
|
| |
change its interface; add modifier functions to add/remove elements from the current routerlist (so we can add indices).
svn:r5276
|
|
|
|
|
|
|
|
| |
printf part was and is limited to at most 1024 byte messages, so having the print
part separately available makes sense.
svn:r5273
|
|
|
|
|
|
| |
protocol so the next guy doesn't blame Nick again
svn:r5245
|
|
|
|
|
|
| |
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:r5191
|
|
|
|
|
|
| |
been an actual error. Normalize whitespace. Enforce convention that "address" is a hostname and "addr" is an IPv4 address.
svn:r5190
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
warn when we'recalling a non-named server by its nickname;
don't warn twice about the same name.
Fix a bug in routers_update_status_from_networkstatus that made nearly
all clients never update routerinfo_t.is_named.
Try to list MyFamily elements by key, not by nickname.
Only warn about names that we generated ourself, or got from the local
user.
On TLS handshake, only check the other router's nickname against its
expected nickname if is_named is set.
svn:r5185
|
|
|
|
| |
svn:r5181
|
|
|
|
|
|
| |
when they have more than 16 router descriptors to download, or when 10 minutes have passed since the last download.
svn:r5166
|
|
|
|
|
|
| |
tree.h
svn:r5149
|
|
|
|
|
|
|
| |
version 0, so don't let version 0 controllers ask for it.
svn:r5107
|
|
|
|
| |
svn:r5106
|
|
|
|
|
|
| |
they do. This should solve the setconf-an-impossible-port bug.
svn:r5046
|
|
|
|
|
|
|
| |
and reduce code duplication in config_free() and option_is_same().
svn:r5040
|
|
|
|
|
|
| |
connection would cause a segfault. (No backport needed since 0.1.0 had only v0 connections.)
svn:r5001
|
|
|
|
| |
svn:r4922
|
|
|
|
|
|
|
| |
option actually mean to set it to ""
svn:r4916
|
|
|
|
| |
svn:r4828
|
|
|
|
|
|
| |
its own, and only dirty our descriptor when we really want to.
svn:r4802
|
|
|
|
|
|
|
| |
will affect them.
svn:r4787
|