Roger Dingledine commited on 2007-03-06 21:28:10
              Zeige 1 geänderte Dateien mit 17 Einfügungen und 3 Löschungen.
            
| ... | ... | 
                      @@ -109,7 +109,7 @@ Windows, Tor uses the standard <tt>select</tt> system  | 
                  
| 109 | 109 | 
                        call, which uses space in the non-page pool. This means  | 
                    
| 110 | 110 | 
                        that a medium sized Tor server will empty the non-page pool, <a  | 
                    
| 111 | 111 | 
                        href="http://wiki.noreply.org/noreply/TheOnionRouter/WindowsBufferProblems">causing  | 
                    
| 112 | 
                        -havoc and crashes</a>. We should probably by using overlapped IO  | 
                    |
| 112 | 
                        +havoc and crashes</a>. We should probably be using overlapped IO  | 
                    |
| 113 | 113 | 
                        instead. One solution would be to teach libevent how to use overlapped IO  | 
                    
| 114 | 114 | 
                        rather than select() on Windows, and then adapt Tor to the new libevent  | 
                    
| 115 | 115 | 
                        interface.</li>  | 
                    
| ... | ... | 
                      @@ -117,7 +117,7 @@ interface.</li>  | 
                  
| 117 | 117 | 
                        high-bandwidth Tor servers end up using dozens of megabytes of memory  | 
                    
| 118 | 118 | 
                        just for buffers. We need better heuristics for when to shrink/expand  | 
                    
| 119 | 119 | 
                        buffers. Maybe this should be modelled after the Linux kernel buffer  | 
                    
| 120 | 
                        -design, where you have many smaller buffers that link to each other,  | 
                    |
| 120 | 
                        +design, where we have many smaller buffers that link to each other,  | 
                    |
| 121 | 121 | 
                        rather than monolithic buffers?</li>  | 
                    
| 122 | 122 | 
                        <li>We need an official central site to answer "Is this IP address a Tor  | 
                    
| 123 | 123 | 
                        server?" questions. This should provide several interfaces, including  | 
                    
| ... | ... | 
                      @@ -125,7 +125,21 @@ a web interface and a DNSBL-style interface. It can provide the most  | 
                  
| 125 | 125 | 
                        up-to-date answers by keeping a local mirror of the Tor directory  | 
                    
| 126 | 126 | 
                        information. Bonus points if it does active testing through each exit  | 
                    
| 127 | 127 | 
                        node to find out what IP address it's really exiting from.</li>  | 
                    
| 128 | 
                        -<li>We need a distributed testing framework. We have unit tests now,  | 
                    |
| 128 | 
                        +<li>We need a measurement study of <a  | 
                    |
| 129 | 
                        +href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>  | 
                    |
| 130 | 
                        +vs <a href="http://www.privoxy.org/">Privoxy</a>. Is Polipo in fact  | 
                    |
| 131 | 
                        +significantly faster, once you factor in the slow-down from Tor? Are the  | 
                    |
| 132 | 
                        +results the same on both Linux and Windows? Related, does Polipo handle  | 
                    |
| 133 | 
                        +more web sites correctly than Privoxy, or vice versa? Are there stability  | 
                    |
| 134 | 
                        +issues on any common platforms, e.g. Windows?</li>  | 
                    |
| 135 | 
                        +<li>It would be great to have a LiveCD that includes the latest  | 
                    |
| 136 | 
                        +versions of Tor, Polipo or Privoxy, Firefox, Gaim+OTR, etc. There are  | 
                    |
| 137 | 
                        +two challenges here: first is documenting the system and choices well  | 
                    |
| 138 | 
                        +enough that security people can form an opinion on whether it should be  | 
                    |
| 139 | 
                        +secure, and the second is figuring out how to make it easily maintainable,  | 
                    |
| 140 | 
                        +so it doesn't become quickly obsolete like AnonymOS. Bonus points if  | 
                    |
| 141 | 
                        +the CD image fits on one of those small-form-factor CDs.</li>  | 
                    |
| 142 | 
                        +<li>We need a distributed testing framework. We have unit tests,  | 
                    |
| 129 | 143 | 
                        but it would be great to have a script that starts up a Tor network, uses  | 
                    
| 130 | 144 | 
                        it for a while, and verifies that at least parts of it are working.</li>  | 
                    
| 131 | 145 | 
                        <li>Right now the hidden service descriptors are being stored on just a  | 
                    
| 132 | 146 |