aboutsummaryrefslogtreecommitdiff
path: root/src/or/directory.c
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2003-09-24 21:24:52 +0000
committerRoger Dingledine <arma@torproject.org>2003-09-24 21:24:52 +0000
commit40d0fca63ae25e9e98b70bd75ce356d63ebc6c45 (patch)
treef433623559193f89f01b6497a8462066d610495a /src/or/directory.c
parent36ec1792d250a9694273c12d832229e077e9bf76 (diff)
downloadtor-40d0fca63ae25e9e98b70bd75ce356d63ebc6c45.tar
tor-40d0fca63ae25e9e98b70bd75ce356d63ebc6c45.tar.gz
cleanups, bugfixes, more verbose logs
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
Diffstat (limited to 'src/or/directory.c')
0 files changed, 0 insertions, 0 deletions