aboutsummaryrefslogtreecommitdiff
path: root/src/or/circuituse.c
Commit message (Collapse)AuthorAge
* Fix a failure case of connection_ap_handshake_attach_circuit()Sebastian Hahn2011-04-28
| | | | | tor_fragile_assert() might be a no-op, so we have to return something here to indicate failure to the caller.
* Allow rend_client_send_introduction to fail transientlyRobert Ransom2011-04-28
| | | | i.e. without closing the AP connection.
* Bump copyright statements to 2011Nick Mathewson2011-01-03
|
* close idle dir-fetch circs earlyRoger Dingledine2010-04-23
|
* Update Tor Project copyright yearsNick Mathewson2010-02-27
|
* Only send reachability status events on overall success/failureRoger Dingledine2009-08-31
| | | | | | | | | We were telling the controller about CHECKING_REACHABILITY and REACHABILITY_FAILED status events whenever we launch a testing circuit or notice that one has failed. Instead, only tell the controller when we want to inform the user of overall success or overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported by SwissTorExit.
* Fixes to spelling fixes. Thanks, Roger!Nick Mathewson2009-05-28
|
* Spell-check Tor.Nick Mathewson2009-05-27
|
* Update copyright to 2009.Karsten Loesing2009-05-04
|
* Retry circuits if the exit node is optional and nonexistant.Nick Mathewson2009-02-09
| | | | | | | | | | | | 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
* If we're using bridges and our network goes away, be more willingRoger Dingledine2009-02-04
| | | | | | | | to forgive our bridges and try again when we get an application request. Bugfix on 0.2.0.x. svn:r18396
* Support 64-bit time_t. Patch from Matthias Drochner. Partial backport ↵Nick Mathewson2009-01-22
| | | | | | candidate. svn:r18234
* actually find the right identity_digest to blame when we getRoger Dingledine2009-01-07
| | | | | | | a destroy cell from our first hop. svn:r17991
* well, that was a disaster. this time for sure.Roger Dingledine2009-01-06
| | | | svn:r17989
* no actual changes besides a seg fault on startup, i meantRoger Dingledine2009-01-06
| | | | svn:r17986
* simplify. no actual changes i think. ;)Roger Dingledine2009-01-06
| | | | svn:r17985
* When our circuit fails at the first hop (e.g. we get a destroyRoger Dingledine2009-01-06
| | | | | | | | | 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
* Remove svn $Id$s from our source, and remove tor --version --version.Nick Mathewson2009-01-04
| | | | | | | | 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
* Downgrade some xxx021s, comment more on others, etcNick Mathewson2008-12-29
| | | | svn:r17823
* Checkpoint my big bug-891 patch.Nick Mathewson2008-12-24
| | | | svn:r17757
* Fix all of the doxygen warnings not pertaining to missing documentation.Nick Mathewson2008-12-22
| | | | svn:r17727
* Downlgrade tweak, and answer lots of XXX021s. No actual code fixes in this ↵Nick Mathewson2008-12-18
| | | | | | patch. svn:r17686
* Remove fixed xxx020s; downgrade unfixed ones.Nick Mathewson2008-12-18
| | | | | | (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
* Move edge-only flags from connection_t to edge_connection_t.Nick Mathewson2008-12-17
| | | | svn:r17643
* Rename or_is_obsolete and move it to or_connection_t where it belongs.Nick Mathewson2008-12-17
| | | | svn:r17642
* fix wide linesNick Mathewson2008-11-07
| | | | svn:r17198
* (a - b) / 2 != a - (b / 2); this is the reason why tunneled directory ↵Karsten Loesing2008-11-05
| | | | | | 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
* Fix an assertion failure on double-marked circuits, and a double-mark.Nick Mathewson2008-11-01
| | | | svn:r17179
* Fix another case of refusing to use a chosen exit node because we think it ↵Nick Mathewson2008-10-21
| | | | | | will reject _mostly_ everything. Based on patch from rovv. See bug 752. svn:r17139
* add patch2 from proposal 155:Roger Dingledine2008-10-15
| | | | | | | | Launch a second client-side introduction circuit in parallel after a delay of 15 seconds (based on work by Christian Wilms). svn:r17108
* put in karsten's patch #1 for proposal 155, modifiedRoger Dingledine2008-10-15
| | | | svn:r17106
* Nobody calls circuit_launch_by_nickname; remove it.Nick Mathewson2008-09-29
| | | | svn:r17006
* Patch from mwenge: update TrackHostExits mapping expiry times when the ↵Nick Mathewson2008-09-29
| | | | | | mappings are used, so that they expire a while after their last use, not a while after their creation. svn:r17004
* Fix a bug where an unreachable relay would establish enoughRoger Dingledine2008-09-29
| | | | | | | | | | | 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
* Add patch 4 from Karsten for proposal 121, slightly modified. Karsten ↵Nick Mathewson2008-09-24
| | | | | | should definitely re-review the bits I changed. svn:r16955
* Add a circuit_conforms_to_options() function for use in debugging paths [and ↵Nick Mathewson2008-09-15
| | | | | | inother stuff too]. Untested, and so far unused. svn:r16914
* karsten's patch for bug 767.Roger Dingledine2008-09-09
| | | | svn:r16808
* Catch and report a few more bootstrapping failure cases when TorRoger Dingledine2008-09-09
| | | | | | | fails to establish a TCP connection. Cleanup on 0.2.1.x. svn:r16803
* r17641@31-33-44: nickm | 2008-08-05 16:07:53 -0400Nick Mathewson2008-08-05
| | | | | | | 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
* note a feature (bugfix) we should do one dayRoger Dingledine2008-08-03
| | | | svn:r16368
* r17436@tombo: nickm | 2008-07-30 09:03:19 -0400Nick Mathewson2008-07-30
| | | | | | | 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
* forward-port r15576Roger Dingledine2008-06-30
| | | | svn:r15577
* If we close our OR connection because there's been a circuitRoger Dingledine2008-06-20
| | | | | | | | pending on it for too long, we were telling our bootstrap status events "REASON=NONE". Now tell them "REASON=TIMEOUT". svn:r15369
* Big bridge bugfixes. Backport candidates.Roger Dingledine2008-06-20
| | | | | | | | | | | | | | | 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
* note a bug that karsten foundRoger Dingledine2008-06-13
| | | | svn:r15236
* r15283@tombo: nickm | 2008-04-22 13:43:45 -0400Nick Mathewson2008-04-22
| | | | | | | Correctly notify one-hop connections when a circuit build has failed. possible fix for bug 669. found by lodger. svn:r14415
* minor fixes that have been accumulatingRoger Dingledine2008-04-16
| | | | svn:r14378
* fix r14162 so it was what i meant. sometimes precedence is surprising!Roger Dingledine2008-03-24
| | | | svn:r14164
* when our onehop circuits were failing, nobody was telling theRoger Dingledine2008-03-24
| | | | | | | | | 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
* If our create-fast cell is mysteriously never answered for a begindirRoger Dingledine2008-03-24
| | | | | | | | 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
generated by cgit v1.2.3 (git 2.25.4) at 2024-10-06 17:51:55 +0000