Mike Perry commited on 2008-03-11 20:12:18
Zeige 1 geänderte Dateien mit 10 Einfügungen und 9 Löschungen.
... | ... |
@@ -557,7 +557,7 @@ also requires a lot of coding. |
557 | 557 |
</li> |
558 | 558 |
|
559 | 559 |
<li> |
560 |
-<b>Tor Exit Scanner Improvements</b> |
|
560 |
+<b>Tor Exit Scanner improvements</b> |
|
561 | 561 |
<br /> |
562 | 562 |
Priority: <i>High</i> |
563 | 563 |
<br /> |
... | ... |
@@ -581,17 +581,17 @@ Ideally, soat.pl would be reimplemented in a sane language with a |
581 | 581 |
robust html parser library (since the rest of Torflow is in Python, |
582 | 582 |
that would be nice, but not required), and calculate signatures only for |
583 | 583 |
tags and content likely to be targeted by a malicious attacker (script |
584 |
-tags, object links, images). It should also be robust in the face of |
|
584 |
+tags, object links, images, css). It should also be robust in the face of |
|
585 | 585 |
changes to content outside of Tor, and ultimately even GeoIP localized |
586 | 586 |
content. |
587 | 587 |
<br /> |
588 |
-This scanner would likely be run by the directory authorities and |
|
588 |
+This scanner would likely be run by the Directory Authorities and |
|
589 | 589 |
report its results to the control port via the AuthDirBadExit config |
590 | 590 |
setting. |
591 | 591 |
<br /> |
592 | 592 |
</li> |
593 | 593 |
<li> |
594 |
-<b>Tor Node Scanner Improvements</b> |
|
594 |
+<b>Tor Node Scanner improvements</b> |
|
595 | 595 |
<br /> |
596 | 596 |
Priority: <i>Medium</i> |
597 | 597 |
<br /> |
... | ... |
@@ -620,7 +620,7 @@ Protocol</a> to |
620 | 620 |
report if a circuit extend through the node succeeds or fails, and |
621 | 621 |
passive statistics can be gathered on both bandwidth and reliability |
622 | 622 |
of other nodes via a node-based monitor using these events. Such a |
623 |
-scanner which would also report information on oddly-behaving nodes to |
|
623 |
+scanner would also report information on oddly-behaving nodes to |
|
624 | 624 |
the Directory Authorities, but a communication channel for this |
625 | 625 |
currently does not exist and would need to be developed as well. |
626 | 626 |
</li> |
... | ... |
@@ -673,10 +673,11 @@ timeframe. Most of these are documented as feature requests in the <a |
673 | 673 |
href="https://bugs.torproject.org/flyspray/index.php?tasks=all&project=5">Torbutton |
674 | 674 |
flyspray section</a>. Good examples include: stripping off node.exit on http |
675 | 675 |
headers, more fine-grained control over formfill blocking, improved referrer |
676 |
-spoofing based on the domain of the site (a-la refspoof extension), tighter |
|
677 |
-integration with Vidalia for reporting Tor status, a New Identity button with |
|
678 |
-Tor integration and multiple identity management, and anything else you might |
|
679 |
-think of. |
|
676 |
+spoofing based on the domain of the site (a-la <a |
|
677 |
+href="http://addons.mozilla.org/firefox/addon/4513">refspoof extension</a>), |
|
678 |
+tighter integration with Vidalia for reporting Tor status, a New Identity |
|
679 |
+button with Tor integration and multiple identity management, and anything |
|
680 |
+else you might think of. |
|
680 | 681 |
|
681 | 682 |
<br /> |
682 | 683 |
|
683 | 684 |