Two suggestions: 1. Include port 80 in the list of long lived ports. 2. Set a limit on circuit build time, so that slow/backlogged nodes don't get used.
CircuitBuildTimeout 10 LongLivedPorts 80,23,21,22,706,1863,5050,5190,5222,5223,6667,8300,8888 That adds 80 (web browsing) to the long lived ports. (Actually, 443 should be added for https:// connections as well), and requires that circuits be constructed in 10 seconds instead of 60. On 2/27/07, sy16 <[EMAIL PROTECTED]> wrote:
I need advice on anonymous v. normal sessions. Tor has saved me from packet sniffers and MITM attacks since I started using it. These attacks always and only happened during my banking sessions. I inferred that my net traffic must have been closely monitored by someone (I have a private-detective neighbor whose son works for my ISP, but I can't very well bring a case based on suspicion). Having enjoyed the protection of Tor, I am now extremely reluctant to get online without it. But sometimes the connections are closed or too slow during my session that I get auto logged out by the server. I have to log in repeatedly, but there are only so many sessions a day allowed, as a security feature. Can someone tell me how best to safeguard my net traffic? ________________________________ What kind of emailer are you? Find out today - get a free analysis of your email personality. Take the quiz at the Yahoo! Mail Championship.
