aboutsummaryrefslogtreecommitdiff
path: root/src/or
diff options
context:
space:
mode:
authorMike Perry <mikeperry-git@fscked.org>2012-12-09 23:50:05 -0800
committerMike Perry <mikeperry-git@fscked.org>2012-12-09 23:50:05 -0800
commitaa16d59ee7abdf7c3309c267052ae265e141e1b3 (patch)
tree0cc65d2290b5bc8f19a2d590783ca23f41b1c670 /src/or
parent4590993ff3d4393caaa1d9d68d04cf0af95c23c7 (diff)
downloadtor-aa16d59ee7abdf7c3309c267052ae265e141e1b3.tar
tor-aa16d59ee7abdf7c3309c267052ae265e141e1b3.tar.gz
Clean up some XXX comments.
Diffstat (limited to 'src/or')
-rw-r--r--src/or/circuitbuild.c4
-rw-r--r--src/or/circuituse.c1
-rw-r--r--src/or/relay.c4
3 files changed, 4 insertions, 5 deletions
diff --git a/src/or/circuitbuild.c b/src/or/circuitbuild.c
index a724006b2..f903bbf09 100644
--- a/src/or/circuitbuild.c
+++ b/src/or/circuitbuild.c
@@ -1434,10 +1434,6 @@ pathbias_check_close(origin_circuit_t *ocirc, int reason)
if (circ->timestamp_dirty) {
/* Any circuit where there were attempted streams but no successful
* streams could be bias */
- // XXX: May open up attacks if the adversary can force connections
- // on unresponsive hosts to use new circs. Vidalia displayes a "Retrying"
- // state.. Can we use that? Does optimistic data change this?
-
log_info(LD_CIRC,
"Circuit %d closed without successful use for reason %d. "
"Circuit purpose %d currently %s.",
diff --git a/src/or/circuituse.c b/src/or/circuituse.c
index d3b480139..cb44bba32 100644
--- a/src/or/circuituse.c
+++ b/src/or/circuituse.c
@@ -1166,6 +1166,7 @@ circuit_has_opened(origin_circuit_t *circ)
* building). */
// XXX: Cannibalized now use RELAY_EARLY, which is visible
// to taggers end-to-end! We really need to probe these instead.
+ // Don't forget to remove this check once that's done!
if (circ->has_opened &&
circ->build_state->desired_path_len > DEFAULT_ROUTE_LEN) {
circ->path_state = PATH_STATE_USE_SUCCEEDED;
diff --git a/src/or/relay.c b/src/or/relay.c
index 3ee0c835b..6ed4b930a 100644
--- a/src/or/relay.c
+++ b/src/or/relay.c
@@ -697,7 +697,9 @@ connection_ap_process_end_not_open(
/* Path bias: If we get a valid reason code from the exit,
* it wasn't due to tagging */
// XXX: This relies on recognized+digest being strong enough not
- // to be spoofable.. Is that a valid assumption?
+ // to be spoofable.. Is that a valid assumption?
+ // Or more accurately: is it better than nothing? Can the attack
+ // be done offline?
circ->path_state = PATH_STATE_USE_SUCCEEDED;
}