[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: anonymous v. normal session
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: anonymous v. normal session
- From: "Michael_google gmail_Gersten" <keybounce@xxxxxxxxx>
- Date: Tue, 27 Feb 2007 23:39:01 -0800
- Delivered-to: archiver@seul.org
- Delivered-to: or-talk-outgoing@seul.org
- Delivered-to: or-talk@seul.org
- Delivery-date: Wed, 28 Feb 2007 02:39:11 -0500
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=g3Vl0l4m1glJf5J7GwgEKnl4ODI6zFDzfTljzv9R2z5R8f/a3n7GPy6YPjq597QX91RU7rw3im0m1NiiqNT+WSR738qPOs1DnHdGi1CK8GlehhRnpDFtCfVcKybHR3cJf/sFCv7VHuEXGMXmi5u97gMOBdZx+lhjVR9LDseg6cU=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Ngcsh/Cxm4UNPxrS79Ag09Gtf1CcxlONUYRRXt0PU0dAg866l4jZXaGsIjPXnJ7fGjA4PcgkcO8Ku3GBh7F2lX/16+4TC6L2Xmf34srtpnBXrSBWGIaBV1ufsso49bk75lwaJdRRE6fvc5gMEAzdOx6BE24cLoqmQK50wcr3+zM=
- In-reply-to: <20070228072119.44449.qmail@web23314.mail.ird.yahoo.com>
- References: <20070228072119.44449.qmail@web23314.mail.ird.yahoo.com>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
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 <sy_c16@xxxxxxxxxxx> 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.