[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Tor design question
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Tor design question
- From: Ringo Kamens <2600denver@xxxxxxxxx>
- Date: Sat, 14 Mar 2009 14:20:25 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Sat, 14 Mar 2009 14:50:57 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:openpgp:content-type:content-transfer-encoding; bh=IZ5aHoxiqRmD5Pr39MRPuGd2LxezK+Djag7NX5V9VhM=; b=S3XF6Pnc7EAN7d0jcNzfHEP8K1TB/AfeTuswL4RIbGGBjuEkDB3fpikeJFsoLkJWDn ttszGf6doFXtqCk1XduztpxNqpbE206gTWSTX0Y2ZDgkVTvk9s55MR3eN83jz7L9ot0Y y7xAFVWzg6sCn5NyJQT47hucKI/zb9HxdmpUY=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:openpgp:content-type :content-transfer-encoding; b=vh9cnGuZV1CVfga+jNREZjX2mAjntcb//MeKubm9KWduYzMgiDPaUc7AXoxAFNa+Td vJHNEpFHPf2PMD5bmH/pHOkXX5ViWvqyymUA4NrZxvHn+KNDYFCIe9V25FNxE6JffMGm 2crYxdQxi8NaGM+qb6Gg21FCrayHBIyXGP9aU=
- In-reply-to: <93e2f71e0903131853h247f205dxa935c925f8ad7f79@xxxxxxxxxxxxxx>
- Openpgp: id=2739044E
- References: <93e2f71e0903131853h247f205dxa935c925f8ad7f79@xxxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Thunderbird 2.0.0.19 (X11/20090105)
As far as I know there's no buffer exploits publicly available for Tor
servers. If there were, the Tor team would patch it very quickly.
Running a firewall wouldn't hurt, just make sure you aren't interfering
with the traffic coming into or out of the Tor network.
Ringo
William Adams wrote:
> I incorrectly posted the following to your blog.
>
> Please ignore the blog post.
>
> *
> *
>
> *Greetings:*
>
> *I gather when running as a relay server, there is a publicly exposed
> listener.
> Is it vulnerable to a buffer exploit?
> if so, what kind of protective firewalling does it need in order for the
> server
> machine to host it safely?*
>
> *Thanks,*
>
> *wlarip*
>