| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, when we had the chosen_exit set but marked optional, and
we failed because we couldn't find an onion key for it, we'd just give
up on the circuit. But what we really want to do is try again, without
the forced exit node.
Spotted by rovv. Another case of bug 752. I think this might be
unreachable in our current code, but proposal 158 could change that.
svn:r18451
|
|
|
|
|
|
|
|
| |
to forgive our bridges and try again when we get an application
request. Bugfix on 0.2.0.x.
svn:r18396
|
|
|
|
|
|
| |
candidate.
svn:r18234
|
|
|
|
|
|
|
| |
a destroy cell from our first hop.
svn:r17991
|
|
|
|
| |
svn:r17989
|
|
|
|
| |
svn:r17986
|
|
|
|
| |
svn:r17985
|
|
|
|
|
|
|
|
|
| |
cell back), avoid using that OR connection anymore, and also
tell all the one-hop directory requests waiting for it that they
should fail. Bugfix on 0.2.1.3-alpha.
svn:r17984
|
|
|
|
|
|
|
|
| |
The subversion $Id$ fields made every commit force a rebuild of
whatever file got committed. They were not actually useful for
telling the version of Tor files in the wild.
svn:r17867
|
|
|
|
| |
svn:r17823
|
|
|
|
| |
svn:r17757
|
|
|
|
| |
svn:r17727
|
|
|
|
|
|
| |
patch.
svn:r17686
|
|
|
|
|
|
| |
(The unfixed ones are being downgraded to regular XXXs mainly on the rationale that they don't seem to be exploding Tor, and they were apparently not showstoppers for 0.2.0.x-final.)
svn:r17682
|
|
|
|
| |
svn:r17643
|
|
|
|
| |
svn:r17642
|
|
|
|
| |
svn:r17198
|
|
|
|
|
|
| |
requests and client-side introduction circuits don't time out after the intended 30 seconds (task #847). Bugfix on r17106. Found by miner.
svn:r17189
|
|
|
|
| |
svn:r17179
|
|
|
|
|
|
| |
will reject _mostly_ everything. Based on patch from rovv. See bug 752.
svn:r17139
|
|
|
|
|
|
|
|
| |
Launch a second client-side introduction circuit in parallel
after a delay of 15 seconds (based on work by Christian Wilms).
svn:r17108
|
|
|
|
| |
svn:r17106
|
|
|
|
| |
svn:r17006
|
|
|
|
|
|
| |
mappings are used, so that they expire a while after their last use, not a while after their creation.
svn:r17004
|
|
|
|
|
|
|
|
|
|
|
| |
reachability testing circuits to do a bandwidth test -- if
we already have a connection to the middle hop of the testing
circuit, then it could establish the last hop by using the existing
connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
circuits no longer use entry guards in 0.2.1.3-alpha.
svn:r16997
|
|
|
|
|
|
| |
should definitely re-review the bits I changed.
svn:r16955
|
|
|
|
|
|
| |
inother stuff too]. Untested, and so far unused.
svn:r16914
|
|
|
|
| |
svn:r16808
|
|
|
|
|
|
|
| |
fails to establish a TCP connection. Cleanup on 0.2.1.x.
svn:r16803
|
|
|
|
|
|
|
| |
Initial conversion of uint32_t addr to tor_addr_t addr in connection_t and related types. Most of the Tor wire formats using these new types are in, but the code to generate and use it is not. This is a big patch. Let me know what it breaks for you.
svn:r16435
|
|
|
|
| |
svn:r16368
|
|
|
|
|
|
|
| |
Move n_addr, n_port, and n_conn_id_digest fields of circuit_t into a separately allocated extend_info_t. Saves 22 bytes per connected circuit_t on 32-bit platforms, and makes me more comfortable with using tor_addr_t in place of uint32_t n_addr.
svn:r16257
|
|
|
|
| |
svn:r15577
|
|
|
|
|
|
|
|
| |
pending on it for too long, we were telling our bootstrap status
events "REASON=NONE". Now tell them "REASON=TIMEOUT".
svn:r15369
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If you have more than one bridge but don't know their keys,
you would only learn a request for the descriptor of the first one
on your list. (Tor considered launching requests for the others, but
found that it already had a connection on the way for $0000...0000
so it didn't open another.)
If you have more than one bridge but don't know their keys, and the
connection to one of the bridges failed, you would cancel all
pending bridge connections. (After all, they all have the same
digest.)
svn:r15366
|
|
|
|
| |
svn:r15236
|
|
|
|
|
|
|
| |
Correctly notify one-hop connections when a circuit build has failed. possible fix for bug 669. found by lodger.
svn:r14415
|
|
|
|
| |
svn:r14378
|
|
|
|
| |
svn:r14164
|
|
|
|
|
|
|
|
|
| |
streams. so they waited 120 seconds before timing out. this
was particularly bad during bootstrapping, if an authority is
down or not answering right.
svn:r14163
|
|
|
|
|
|
|
|
| |
attempt, notice more quickly. Some of our bootstrapping attempts have a 60
second delay while we sit there wondering why we're getting no response.
svn:r14162
|
|
|
|
|
|
|
| |
Part of fix for bug 617: allow connection_ap_handshake_attach_circuit() to mark connections, to avoid double-mark warnings. Note that this is an incomplete refactoring.
svn:r14066
|
|
|
|
|
|
|
| |
More 64-to-32 fixes.
svn:r13672
|
|
|
|
|
|
|
| |
Do the last part of arma's fix for bug 437: Track the origin of every addrmap, and use this info so we can remove all the trackhostexits-originated mappings for a given exit.
svn:r13660
|
|
|
|
|
|
|
| |
work, nobody had ever implemented it. Bugfix on 0.1.0.x.
svn:r13647
|
|
|
|
|
|
|
| |
Bugfix from Karsten Loesing: Retry v2 rend descriptors on intro point failure.
svn:r13431
|
|
|
|
| |
svn:r13412
|
|
|
|
|
|
|
| |
Refactor circuit_launch* functions to take a bitfield of flags rather than 4 separate nonconsecutive flags arguments. Also, note a possible but in circuit_find_to_cannibalize, which seems to be ignoring its purpose argument.
svn:r12948
|
|
|
|
| |
svn:r12786
|
|
|
|
| |
svn:r12571
|