it policy is in that case. I'm not even
> sure a bridge can have an exit policy, since it isn't an exit..
Sorry I think I've misunderstood slightly. I thought you were asking
about running Tor itself. I am not familiar with the obfuscating
proxy part of Tor so I don't know how it interacts with exit
policies. I suggest asking the Tor developers.
If it sends packets to the normal Internet like a Tor exit node does
then yes you do need to block ports 25 and 22, but that might be
taken care of by your usual exit policy.
Cheers,
Andy
--=20
http://bitfolk.com/ -- No-nonsense VPS hosting
--6s/G0Ait2f6IH9MX
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAk82mUAACgkQIJm2TL8VSQsy9wCg2FyfwGFgd8o8Ppp/p56Gz1Pk
zq8An0/5aTQ8rsQYRs222KGA6X0V9LqC
=6VTb
-----END PGP SIGNATURE-----
--6s/G0Ait2f6IH9MX--
From danielcase10@??? Sat Feb 11 16:38:27 2012
Received: from mail-lpp01m010-f48.google.com ([209.85.215.48])
by mail.bitfolk.com with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16)
(Exim 4.72) (envelope-from <danielcase10@???>)
id 1RwFxz-0005lQ-66
for users@???; Sat, 11 Feb 2012 16:38:27 +0000
Received: by lagw12 with SMTP id w12so4540342lag.21
for <users@???>; Sat, 11 Feb 2012 08:38:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:cc:content-type;
bh=2zaWZRAFpXGwuGJ2CCAV+Q0i1W+wMqpI6wWSW0sDDYc=;
b=L02jeZ2qPTJZRh09O9LRf7tHmXAb+1XklxtmKhZ3E/utX+/v8DKi9R2RDxz9yFECXs
xZV5I0/DrIrk8+prtzOCFbf9ItcuvUD7O9+96LbK6SDoGohkUlQDwPRkOS/nqqXzNgoL
3xmph6s1dXdPMzS0L7ZYLOrG/slRMy6cjwnmg=
Received: by 10.112.100.34 with SMTP id ev2mr3617370lbb.13.1328978301161; Sat,
11 Feb 2012 08:38:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.152.112.232 with HTTP; Sat, 11 Feb 2012 08:38:01 -0800 (PST)
In-Reply-To: <20120211163138.GV32046@???>
References: <CALdaYd06o3HAm_p+C7Qn87FJJbBftEiEm1FMBs_dDf4PkNF5yA@???>
<20120211152619.GF23380@???>
<CALdaYd3_K6W9s-E7ErUY68xXqFsB3rZxWEFCDAGBbvYRd+3CpA@???>
<20120211163138.GV32046@???>
From: Daniel Case <danielcase10@???>
Date: Sat, 11 Feb 2012 16:38:01 +0000
Message-ID: <CALdaYd2FnyfHjn1b9CJ=RMeXXhomnmnnj4L3UoYjfDgJRmgthg@???>
To: Andy Smith <andy@???>
Content-Type: text/plain; charset=ISO-8859-1
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Sat,
11 Feb 2012 16:38:27 +0000
X-SA-Exim-Connect-IP: 209.85.215.48
X-SA-Exim-Mail-From: danielcase10@???
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
spamd2.lon.bitfolk.com
X-Spam-Level:
X-Spam-ASN: AS15169 209.85.128.0/17
X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU, RCVD_IN_DNSWL_LOW,
SPF_PASS shortcircuit=no autolearn=disabled version=3.3.1
X-Spam-Report: * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/,
low * trust * [209.85.215.48 listed in list.dnswl.org]
* -0.0 SPF_PASS SPF: sender matches SPF record
* -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's * domain
* -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
* 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily
* valid
X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000)
X-SA-Exim-Scanned: Yes (on mail.bitfolk.com)
Cc: users@???
Subject: Re: [bitfolk] Tor Obsfucation
X-BeenThere: users@???
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
<mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
<mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Sat, 11 Feb 2012 16:38:27 -0000
Hey Andy,
The Iranian government have stopped access to SSL and most encrypted
channels, which means it is impossible for my college friends who went
back this year (and the rest of the Iranian population) to connect to
Tor and most anonymizers via normal methods.
Tor have retaliated by releasing an obfuscation proxy which means
people can connect "under the radar".
From hrm@??? Sat Feb 11 16:52:25 2012
Receive