| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
circuits, even when SocksPort is off.
svn:r1327
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
successful/failed connections, successful/failed extends, and
connection uptimes.
It's still not done: more tests are needed, and not everything calls
connection/circuit_mark_for_close properly. This skews the results.
Also, there needs to be a 'testing' mode for non-OP ORs, where they
periodically build circuits just to test whether extends work.
svn:r1313
|
|
|
|
|
|
| |
or tested yet.
svn:r1310
|
|
|
|
|
|
|
|
| |
bugfix: don't return immediately for has_pending_tls_data unless
the conn is allowed to read
svn:r1270
|
|
|
|
|
|
|
|
| |
this is a checkpoint commit; there still remain some
bugs, er, somewhere.
svn:r1269
|
|
|
|
| |
svn:r1258
|
|
|
|
| |
svn:r1257
|
|
|
|
| |
svn:r1247
|
|
|
|
| |
svn:r1242
|
|
|
|
|
|
| |
implements the new spec. Uses more RAM, but not so you would notice.
svn:r1235
|
|
|
|
| |
svn:r1225
|
|
|
|
| |
svn:r1209
|
|
|
|
|
|
|
| |
also rename AP_CONN_STATE_CONNECTING to _CONNECT_WAIT
svn:r1208
|
|
|
|
|
|
| |
is down
svn:r1206
|
|
|
|
| |
svn:r1197
|
|
|
|
|
|
|
|
|
|
|
| |
Apparently, when a DNS failure was already cached, then when we tried
to mark the exit connection as closed, we'd try to remove it from the
pending queue anyway, and hit an assert. Now, we put failed-resolve
connections in a separate state so that mark_for_close does the right
thing.
svn:r1196
|
|
|
|
| |
svn:r1176
|
|
|
|
| |
svn:r1175
|
|
|
|
|
|
|
|
| |
resolve in response to a DNS worker dying) and connection_dns_remove (remove
a pending connection from the resolve structure.)
svn:r1168
|
|
|
|
| |
svn:r1163
|
|
|
|
| |
svn:r1155
|
|
|
|
|
|
| |
only a close path; add some missing end cells; change return conventions a little.
svn:r1149
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
who wants to shut down a connection calls connection_mark_for_close instead
of setting marked_for_close to 1. This automatically removes the connection
from the DNS cache if needed, sends a RELAY END cell if appropriate, and can
be changed to do whatever else is needed.
Still to do:
- The same for circuits, maybe.
- Add some kind of hold_connection_open_until_flushed flag, maybe.
- Change stuff that closes connections with return -1 to use mark_for_close,
maybe.
svn:r1145
|
|
|
|
|
|
|
|
|
|
| |
add some more data to be flushed but never turn POLLOUT on. not sure
how commonly this bug was hit, but it would be a doozy.
Also add some asserts to see if it happens elsewhere.
svn:r1142
|
|
|
|
|
|
|
|
| |
Now it reloads the RouterFile (or default dirservers) if it has no
dirservers.
svn:r1130
|
|
|
|
| |
svn:r1126
|
|
|
|
|
|
|
|
|
| |
plus provide an internal dirservers file if they don't have one
having no config files will make it easier to run on windows
svn:r1124
|
|
|
|
|
|
|
|
| |
corruption faster; also, check for corruption in dns.c so we can fail fast
for the bug that's nailing Lucky and moria3.
svn:r1123
|
|
|
|
|
|
| |
to sometimes not work.
svn:r1114
|
|
|
|
|
|
|
|
|
| |
if your exitpolicy includes " *:*" then it is final,
else we append the default exit policy.
(thanks weasel)
svn:r1105
|
|
|
|
|
|
|
|
| |
Create ExitPolicyPrepend config parameter, to customize the default
exit policy.
svn:r1103
|
|
|
|
|
|
|
| |
maybe it works now.
svn:r1101
|
|
|
|
|
|
| |
was: "maybe reject,accept" should be "maybe", not "accept".
svn:r1093
|
|
|
|
| |
svn:r1011
|
|
|
|
| |
svn:r1008
|
|
|
|
|
|
|
|
|
|
|
| |
we're not entirely migrated to burst yet, for backward compatibility
note some win32 probable-bugs
clean up routerlist.c
svn:r982
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were telling a child to die by closing the parent's file descriptor
to him. But newer children were inheriting the open file descriptor from
the parent, and since they weren't closing them, the socket never closed,
so the child never read eof, so he never knew to exit.
As a side effect to this bug, we were probably failing to properly close
connections to remote hosts, ORs, and OPs, after a dns child was born.
I'm surprised Tor worked at all.
svn:r974
|
|
|
|
|
|
|
| |
(i think ;)
svn:r971
|
|
|
|
|
|
|
| |
now it's a char[4] rather than an int
svn:r966
|
|
|
|
|
|
|
|
| |
include the infrastructure for inserting padding cells when there's
a relay-recognized conflict, but it does not work currently.
svn:r958
|
|
|
|
| |
svn:r955
|
|
|
|
|
|
|
| |
change message when using non-recommended tor version
svn:r954
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
split 7-byte stream_id string into 2-byte recognized and 2-byte stream_id
fix two seg faults in fetch_from_buf_http
fix several lurking seg faults in handling unexpected relay cells
still need to
* clean up relay_crypt
* use relay dummies if there's going to be a conflict with rh.recognized
* check for a conflict when generating stream_ids
svn:r953
|
|
|
|
| |
svn:r951
|
|
|
|
|
|
|
|
|
|
| |
than use fixed-size strings
reorganize directory_handle_command so it'll be easier to do more with
our directory servers
svn:r950
|
|
|
|
|
|
|
|
| |
make circuit_consider_sending_sendme use connection_edge_send_command
fix endian bug in relay length handling (maybe)
svn:r946
|
|
|
|
|
|
|
|
|
| |
move length to 2 bytes, put it in the relay header
remove 4 reserved bytes in cell
add 4 bytes to relay header for the integrity check
svn:r942
|
|
|
|
|
|
|
|
|
|
| |
verify it at the client end
abstract the onionskin handshake lengths
breaks backward compatibility (again)
svn:r941
|
|
|
|
| |
svn:r932
|
|
|
|
| |
svn:r929
|