[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Bug: improperly bound listen addresses?
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Bug: improperly bound listen addresses?
- From: grarpamp <grarpamp@xxxxxxxxx>
- Date: Fri, 1 Aug 2008 03:17:15 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Fri, 01 Aug 2008 03:17:23 -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:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=Uue6iBikhO6uY0349ZJoSpHast6mtXOsF6pk7/CXG/0=; b=XkKAooMJTwCIpDbKpmZStxxLqLrU6ztNNV1o0Sr2WKKL0ecY7zES0gUt54JpYA9dt0 I0SjyJZ50QpNtmXvLzAdQvxgTVmdJN1YlSWXsRGp0DxRe2tnNZGko1JH4wrEQKwZjZDz uFOQ+yP5RUaAoxl/A3z/CCxJwSGr/CrD7IQdE=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=MDbUaPnMoG1yhdEZqN1Ib30Nmt+Rm7pZEaynGMaDQmvhxPVNllQvMkwaFI5fVsyY+m CBGJqxpWLxRIxG+kg3UrEKnZrz1RJEI72BRCbNhFp+O7g/mAbeiEf6Rf7/gluhfPSRF7 xEFAO4Wj1730C5ivih/lV8F6x0Rds/T9yeanw=
- In-reply-to: <200808010600.m7160BAk000145@xxxxxxxxxxxxx>
- References: <200808010600.m7160BAk000145@xxxxxxxxxxxxx>
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
> secured ports as client ports rather than server ports.
To appear to the casual inspector to be a named. To get around those
filtering dns requests from ports other than 53. Named commonly
listens on 53. But it may also send from 53 if so configured.
Different environments have different rules.
> The routines in resolv.conf
Ahh, yes. Ok, Tor is not likely to be a named anytime soon :) I'll
fire up a named, bind it as desired and point Tor at it.
> If you have entered a host+domainname on the Address line in
> torrc, tor also needs to be able to resolve that address.
Hey, that just might be the source of those warning messages I first
posted in this thread. It may be 'guessing' wrong even though I
told it where to bind OR and DIR...ok, tested, that's the bug.
Updating ticket.
Address _address_
The IP address or fqdn of this server (e.g. moria.mit.edu).
You can leave this unset, and Tor will guess your IP address.