aboutsummaryrefslogtreecommitdiff
path: root/src/or/relay.c
diff options
context:
space:
mode:
authorMike Perry <mikeperry-git@fscked.org>2012-12-10 00:28:07 -0800
committerMike Perry <mikeperry-git@fscked.org>2012-12-10 00:28:07 -0800
commitd409c8a90d876c2f45a1c4ea14ddae44fa7c8f18 (patch)
tree18cee69a1157b9d4a944a625bafc84f6d8a9c9cc /src/or/relay.c
parent43a00877cf01888229d5d34085a2b75748848af1 (diff)
downloadtor-d409c8a90d876c2f45a1c4ea14ddae44fa7c8f18.tar
tor-d409c8a90d876c2f45a1c4ea14ddae44fa7c8f18.tar.gz
More log message and space fixups.
Diffstat (limited to 'src/or/relay.c')
-rw-r--r--src/or/relay.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/or/relay.c b/src/or/relay.c
index 6ed4b930a..fd8f8579a 100644
--- a/src/or/relay.c
+++ b/src/or/relay.c
@@ -697,7 +697,7 @@ 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;