| Commit message (Collapse) | Author | Age |
|
|
|
| |
svn:r1450
|
|
|
|
|
|
|
|
|
|
|
| |
* read all the time (before we would ignore eof sometimes, oops)
* we can handle different urls now
* send back 404 for an un-handled url
* commands initiated by the client can handle payloads now
* introduce conn->purpose to avoid exponential state-space explosion
svn:r1400
|
|
|
|
|
|
|
| |
than flushing them, if they were timing out before we marked them
svn:r1366
|
|
|
|
| |
svn:r1356
|
|
|
|
|
|
|
|
| |
when an AP connection dies early, be sure to do a socks reject
for it. if you just hang up, tsocks goes into an infinite loop.
svn:r1352
|
|
|
|
|
|
|
| |
expect it to have a nickname.
svn:r1351
|
|
|
|
| |
svn:r1335
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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:r1264
|
|
|
|
| |
svn:r1258
|
|
|
|
| |
svn:r1248
|
|
|
|
| |
svn:r1247
|
|
|
|
|
|
|
| |
it's simply not true
svn:r1236
|
|
|
|
| |
svn:r1225
|
|
|
|
|
|
|
|
|
|
| |
we were never writing anything when hold_open_until_flushed was set,
since conn_write returns early if marked_for_conn is set.
seems a bit better now.
svn:r1214
|
|
|
|
| |
svn:r1212
|
|
|
|
|
|
|
| |
and also note/fix a variety of other stream-based bugs
svn:r1210
|
|
|
|
| |
svn:r1209
|
|
|
|
| |
svn:r1203
|
|
|
|
| |
svn:r1202
|
|
|
|
|
|
|
|
|
|
|
| |
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:r1174
|
|
|
|
|
|
|
|
| |
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:r1162
|
|
|
|
|
|
|
| |
we weren't actually asserting much. oops.
svn:r1160
|
|
|
|
| |
svn:r1159
|
|
|
|
|
|
|
| |
still plenty more left to clean
svn:r1158
|
|
|
|
| |
svn:r1152
|
|
|
|
|
|
| |
only a close path; add some missing end cells; change return conventions a little.
svn:r1149
|
|
|
|
| |
svn:r1148
|
|
|
|
| |
svn:r1147
|
|
|
|
| |
svn:r1146
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
arrives, then the stream wasn't getting removed from the pending list.
this may have been the lucky-bug.
this commit may also not actually fix the bug. it's darn hard to
reproduce.
svn:r1122
|
|
|
|
| |
svn:r1118
|
|
|
|
|
|
|
| |
e.g., this breaks directory service
svn:r1033
|
|
|
|
| |
svn:r1011
|
|
|
|
| |
svn:r1009
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
breaks in part-way through can't learn how many circs/streams have
been made
svn:r960
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
make circuit_consider_sending_sendme use connection_edge_send_command
fix endian bug in relay length handling (maybe)
svn:r946
|