aboutsummaryrefslogtreecommitdiff
path: root/src/or
Commit message (Expand)AuthorAge
* Short-term fix: prevent possible segfault in connection_close_unattached_ap•••svn:r3970 Nick Mathewson2005-04-01
* when you decide you're reachable, actually publish your descriptor•••right then. svn:r3968 Roger Dingledine2005-04-01
* require exactly 0.0.9.7 for middle hops of testing circs, for now•••svn:r3967 Roger Dingledine2005-04-01
* when building testing circuits, always use middle hops•••running at least 0.0.9.7 svn:r3966 Roger Dingledine2005-04-01
* fix assert: if our dirport isn't reachable yet, don't trick•••*ourselves* into thinking the dirport is zero. but continue to tell other people that it is. svn:r3952 Roger Dingledine2005-04-01
* when the or-connect succeeded and the tls handshake succeeded•••but we didn't like the result, we were closing the connection without sending any destroys back for the pending circuits. now send those destroys anyway; i hope this doesn't break too much. svn:r3951 Roger Dingledine2005-04-01
* fix typo in earlier libevent mmessage suppress patch•••svn:r3950 Nick Mathewson2005-04-01
* authdirservers shouldn't do orport reachability detection,•••since they're in clique mode, so it will be rare to find a server not already connected to them. svn:r3949 Roger Dingledine2005-04-01
* Add code to suppress spurious libevent log msgs; use it to resolve bug 68.•••svn:r3948 Nick Mathewson2005-04-01
* fix some log spacing problems•••svn:r3942 Roger Dingledine2005-04-01
* Use recent libevent features when possible•••svn:r3940 Nick Mathewson2005-04-01
* Patch: when extending to an unknown router, compare identity to expected iden...•••svn:r3937 Nick Mathewson2005-03-31
* spell recommended correctly•••svn:r3936 Roger Dingledine2005-03-31
* still publish your descriptor if orport is reachable but dirport isn't•••when building testing circs for orport testing, require high-bandwidth nodes, so fewer circs fail. complain about unreachable orport separately from unreachable dirport. svn:r3935 Roger Dingledine2005-03-31
* redo the state descriptors now that we have a controller-wait state•••svn:r3934 Roger Dingledine2005-03-31
* ...and use it to make sure we only conclude reachability if•••we didn't initiate the conn. svn:r3932 Roger Dingledine2005-03-31
* Fix bug in redirectstream.•••svn:r3926 Nick Mathewson2005-03-31
* mark two more bugs. nick, can you take a look?•••svn:r3920 Roger Dingledine2005-03-29
* don't check for reachability, and don't whine about it, while we're•••hibernating. svn:r3919 Roger Dingledine2005-03-29
* resolve another 'hasn't sent end yet' bug•••svn:r3911 Roger Dingledine2005-03-29
* Fix a couple more places where we use ->new_address without checking that it ...•••svn:r3907 Nick Mathewson2005-03-28
* make calls to address_is_in_virtual_range more bullet-proof.•••might fix the assert failure i just got. svn:r3906 Roger Dingledine2005-03-28
* Clarify that we don't, and why we don't, need to redefine FD_SETSIZE.•••svn:r3904 Nick Mathewson2005-03-28
* we seem to have lost our define for FD_SETSIZE on win32 in the change•••from fakepoll to libevent. be sure to define it *before* we include winsock. svn:r3903 Roger Dingledine2005-03-27
* but only do the rapid reachability testing if we're hoping to be a server.•••svn:r3902 Roger Dingledine2005-03-27
* forward-port the fixing of the crash bug.•••svn:r3900 Roger Dingledine2005-03-27
* if your server hasn't found itself to be reachable, complain every•••20 minutes, not just once. svn:r3897 Roger Dingledine2005-03-27
* clean up socks reply stuff more.•••add a few more reasons so we can be more informative. svn:r3895 Roger Dingledine2005-03-27
* Rename ManageConnections to LeaveStreamsUnattached. Apparently, there was a ...•••svn:r3894 Nick Mathewson2005-03-27
* stop most cases of hanging up on a socks connection without sending•••the socks reject. audit for remaining ones. also make things more uniform so we always remember to hold-open-until-flushed, etc. svn:r3891 Roger Dingledine2005-03-27
* move the assert higher up so the error message makes more sense•••next time. svn:r3887 Roger Dingledine2005-03-26
* fix assert: stop trying to send a socks reply to an *exit*•••connection when we get an end cell before it's finished opening. svn:r3886 Roger Dingledine2005-03-26
* try harder to establish reachability, in the first 20 minutes•••of uptime. svn:r3884 Roger Dingledine2005-03-26
* make it clearer to the human that his server is testing•••its reachability. tell him when it succeeds, or when 20 minutes pass and it hasn't succeeded yet. svn:r3882 Roger Dingledine2005-03-26
* and fill in another missing socks reply•••svn:r3877 Roger Dingledine2005-03-25
* fix another case where we need to send a socks reply (reject)•••back before we close the conn. svn:r3876 Roger Dingledine2005-03-25
* remove dead code•••svn:r3875 Roger Dingledine2005-03-25
* don't mark a router down just because your httpsproxy is unreachable•••svn:r3874 Roger Dingledine2005-03-25
* Note where connection that hasnt sent end was marked.•••svn:r3872 Nick Mathewson2005-03-25
* REUSEADDR on normal places means you can rebind to the port•••right after somebody else has let it go. But REUSEADDR on win32 means to let you bind to the port _even when somebody else already has it bound_. So, don't do that on Win32. svn:r3867 Roger Dingledine2005-03-24
* forward-port the circuit_resume_edge_reading_helper fix.•••svn:r3863 Roger Dingledine2005-03-24
* when you attachstream to a circid of 0, send back an answer•••svn:r3857 Roger Dingledine2005-03-24
* cleanup so connection_ap_handshake_attach_chosen_circuit() always•••gets open circs. svn:r3856 Roger Dingledine2005-03-24
* Bulletproof connection_ap_handshake_attach_chosen_circuit•••svn:r3855 Nick Mathewson2005-03-24
* Fix SOCKS5 bug: Set replylen to 0 after sending hanshake back•••svn:r3850 Nick Mathewson2005-03-24
* Debug EXTENDCIRCUIT•••svn:r3849 Nick Mathewson2005-03-24
* fix an assert -- we're not allowed to write onto a conn after we've•••connection_unregistered it. there's still more work to be done here, since we need to make sure to send back the socks-reply as soon as we know what it will be -- we can't just wait until connection-about-to-close to deal with it. svn:r3847 Roger Dingledine2005-03-23
* fix an over-eager assert, to make httpsproxy get a little farther•••svn:r3846 Roger Dingledine2005-03-23
* forward-port the commenting out of the assert that glenn fink was•••triggering. we still don't know why he was triggering it. svn:r3841 Roger Dingledine2005-03-23
* Fix bug 44: on HUP, if descriptor building fails (say, because router_get_my_...•••svn:r3839 Nick Mathewson2005-03-23