| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
| |
fix badness in usage()
if neither socksport nor orrport is defined, quit
obsolete connection_flush_buf()
svn:r780
|
|
|
|
|
|
|
|
|
| |
exit if bind fails
add usage printfs
rearrange config options for readability
svn:r674
|
|
|
|
|
|
|
| |
move default exit policy into config files
svn:r653
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
setuid and setgid respectively, and die if it can't.
(If the User option is set, tor will setgid to the user's gid as well.)
This happens after the pidfile is created, so that in cases where tor
needs to be root to work with the pidfile, it will at least be able to
create it, although it won't be able to delete it. That sucks, but
it's somewhat better than not being able to create the pidfile in the
first place.
svn:r652
|
|
|
|
|
|
|
|
| |
rename APPort to SocksPort
introduce new tor_free() macro
svn:r642
|
|
|
|
| |
svn:r634
|
|
|
|
|
|
|
|
|
|
|
|
| |
If DebugLogFile is specified, log to it at -l debug
If LogFile is specified, log to it at the -l from the commandline
(default info)
If no LogFile *and* not a Daemon, then log to stdout.
Make conn->s = -1 by default (this might break things)
When kill -USR1, prefer to log at INFO, but make sure they always see it.
svn:r596
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
correctly based on how configure was run
- cause tor to guess the location of torrc more intelligently
- cause cause src/config/torrc and src/conf/sample-server-torrc to be
generated with contents that are correct for the way configure was
run
- cause "make install" to put torrc, sample-server-torrc, and
dirservers somewhere intelligent
svn:r587
|
|
|
|
|
|
|
| |
and fix a few typos
svn:r571
|
|
|
|
|
|
|
| |
(patch courtesy aaron turner)
svn:r565
|
|
|
|
| |
svn:r564
|
|
|
|
| |
svn:r560
|
|
|
|
| |
svn:r552
|
|
|
|
| |
svn:r551
|
|
|
|
| |
svn:r538
|
|
|
|
|
|
|
| |
ACIs are decided now by strcmp'ing nicknames, rather than comparing addr:port
svn:r529
|
|
|
|
| |
svn:r523
|
|
|
|
|
|
|
| |
still not finished integrating new dirserv stuff
svn:r507
|
|
|
|
| |
svn:r496
|
|
|
|
| |
svn:r494
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ERR is if something fatal just happened
WARNING is something bad happened, but we're still running. The bad thing
is either a bug in the code, an attack or buggy protocol/implementation
of the remote peer, etc. The operator should examine the bad thing and
try to correct it.
(No error or warning messages should be expected. I expect most people
to run on -l warning eventually.)
NOTICE is never ever used.
INFO means something happened (maybe bad, maybe ok), but there's nothing
you need to (or can) do about it.
DEBUG is for everything louder than INFO.
svn:r486
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
'buf_t' is now an opaque type defined in buffers.c .
Router descriptors now include all keys; routers generate keys as
needed on startup (in a newly defined "data directory"), and generate
their own descriptors. Descriptors are now self-signed.
Implementation is not complete: descriptors are never published; and
upon receiving a descriptor, the directory doesn't do anything with
it.
At least "routers.or" and orkeygen are now obsolete, BTW.
svn:r483
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixed up the assert_*_ok funcs some (more work remains)
Changed config so it reads either /etc/torrc or the -f arg, never both
Finally tracked down a nasty bug with our use of tls:
It turns out that if you ask SSL_read() for no more than n bytes, it
will read the entire record from the network (and maybe part of the next
record, I'm not sure), give you n bytes of it, and keep the remaining
bytes internally. This is fine, except our poll-for-read looks at the
network, and there are no bytes pending on the network, so we never know
to ask SSL_read() for more bytes. Currently I've hacked it so if we ask
for n bytes and it returns n bytes, then it reads again right then. This
will interact poorly with our rate limiting; we need a cleaner solution.
svn:r481
|
|
|
|
| |
svn:r451
|
|
|
|
|
|
|
|
| |
write new certfile if you don't have one already
set up a tls context on startup
svn:r432
|
|
|
|
| |
svn:r430
|
|
|
|
|
|
|
|
|
| |
your client exits if you're running a version not in the
directory's list of acceptable versions (unless you have a
config variable set to override).
svn:r408
|
|
|
|
|
|
|
|
|
| |
add NumCpus config variable in preparation for cpuworkers
hardcode /etc/torrc path for config (simplifies win32 port)
improve exit policy debugging during router entry parsing
svn:r397
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- signal support
- forking for DNS farm
- changes for async IO
- daemonizing
In other words, some files still don't build, and the ones that do build,
do nonblocking IO incorrectly.
I'm also not checking in the project files till I have a good place
for them.
svn:r380
|
|
|
|
| |
svn:r365
|
|
|
|
| |
svn:r333
|
|
|
|
| |
svn:r298
|
|
|
|
|
|
|
|
|
|
| |
remove sendme cells
replace malloc with tor_malloc
patch (but not track down) bug in onion pending list
streamline connection_ap handshake
svn:r293
|
|
|
|
| |
svn:r274
|
|
|
|
| |
svn:r241
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
separate file.
svn:r224
|
|
|
|
| |
svn:r205
|
|
|
|
|
|
|
|
| |
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:r184
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
first cut, probably needs more playing with
svn:r137
|
|
|
|
|
|
|
| |
reformat parts of onion.c
svn:r136
|
|
|
|
| |
svn:r133
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
proxies now periodically pull down an hourly-updated directory,
and replace their router list with it if it parses correctly.
svn:r112
|
|
|
|
| |
svn:r96
|