[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [or-cvs] [tor/master] Disable .exit notation unless AllowDotExit is 1.
- To: or-dev@xxxxxxxxxxxxx
- Subject: Re: [or-cvs] [tor/master] Disable .exit notation unless AllowDotExit is 1.
- From: coderman <coderman@xxxxxxxxx>
- Date: Tue, 11 Aug 2009 20:46:49 -0700
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-dev-outgoing@xxxxxxxx
- Delivered-to: or-dev@xxxxxxxx
- Delivery-date: Tue, 11 Aug 2009 23:46:53 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=iiA/BCGV9NoA7/ypzvsw2ZXV4kV5XHg2D9sUx3t0tfA=; b=M9JOWy/IhIZoyRcrF5EKDwCGeyf2dzP+X6aA2MFPmf2eKtk8vKTG9Tob7VQfk3RZZK 7pdzrwe/dwYUqtDW+3TgkwjRTYKclEQFDfvmiVKP5SKEd3fxKFHHLETv1oeyuXQeZX35 4wYmaoRZoyPwVSwMEzN6tZjRP+5+ahC+IcnLc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=oQjYRaPPLj+PgmdznX/mUQCRzvgo1n9UkJLeQ42emcRA7LvUaSUwlgX4TsWH/euG7X J3FAIbxLW82ajlbnRPweC0AUSkAcAaSsIww+4FkoGQTddd5J1cAwYhnOSkydChw918cD /D9V7DtDJK0DSP/eviKmCFpLg98vp4ApLfkT8=
- In-reply-to: <20090811203350.75f98c59@xxxxxxxxxx>
- References: <20090810014857.105A6140738F@xxxxxxxxxxxxxx> <20090811203350.75f98c59@xxxxxxxxxx>
- Reply-to: or-dev@xxxxxxxxxxxxx
- Sender: owner-or-dev@xxxxxxxxxxxxx
On Tue, Aug 11, 2009 at 11:33 AM, Fabian
Keil<freebsd-listen@xxxxxxxxxxxxx> wrote:
> ...
> Passing the exit notation through the TransPort or the NatdPort will
> be challenging given that Tor only gets the destination IP address.
the TransPort is intended to be used with DNSPort, thus .exit notation
will auto map to a private address like .onions do and facilitate the
same path manipulation.
setting AutomapHostsSuffixes config option with .onion only can avoid
this for transparent Tor users with older versions. (but SOCKS still
an issue).
best regards,