Delivery-Date: Sun, 12 Jun 2016 16:32:34 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [138.201.14.202])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 630231E01A6;
	Sun, 12 Jun 2016 16:32:32 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C8F07E174D;
	Sun, 12 Jun 2016 20:32:23 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B87C1E16C0
 for <tor-talk@lists.torproject.org>; Sun, 12 Jun 2016 20:32:17 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id BFxvwOveHyyl for <tor-talk@lists.torproject.org>;
 Sun, 12 Jun 2016 20:32:17 +0000 (UTC)
Received: from len.romanrm.net (len.romanrm.net [IPv6:2001:bc8:3829:400::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 83F1AE1736
 for <tor-talk@lists.torproject.org>; Sun, 12 Jun 2016 20:32:17 +0000 (UTC)
Received: from natsu (unknown [IPv6:fd39::e9:9eff:fe8f:1bcf])
 by len.romanrm.net (Postfix) with SMTP id E8CD16BA33;
 Sun, 12 Jun 2016 20:21:34 +0000 (UTC)
Date: Mon, 13 Jun 2016 01:21:23 +0500
From: Roman Mamedov <rm@romanrm.net>
To: gdfg dfgf <torrio888@net.hr>
Message-ID: <20160613012123.3e4d9fe0@natsu>
In-Reply-To: <20160613011708.17b2f696@natsu>
References: <20160612215634.682F2381@net.hr>
	<20160613011708.17b2f696@natsu>
X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Cc: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] 2 hop mode for people that only want to use Tor for
 censorship circumvention to conserve bandwidth and decrease latency?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Reply-To: tor-talk@lists.torproject.org
Content-Type: multipart/mixed; boundary="===============8246978189152357701=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

--===============8246978189152357701==
Content-Type: multipart/signed; micalg=pgp-sha1;
 boundary="Sig_/plHRhUbaov1un34GxkJ8OQ5"; protocol="application/pgp-signature"

--Sig_/plHRhUbaov1un34GxkJ8OQ5
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Mon, 13 Jun 2016 01:17:08 +0500
Roman Mamedov <rm@romanrm.net> wrote:

> > entry node---> exit node ---> website
>=20
> You don't even need 2 hops in this case. Why not propose 1-hop?

Oh actually, just remembered reading about that somewhere -- and turns out =
it
was in Tor's own man page:

       AllowSingleHopCircuits 0|1
           When this option is set, the attached Tor controller can use rel=
ays
           that have the AllowSingleHopExits option turned on to build one-=
hop
           Tor connections. (Default: 0)

       AllowSingleHopExits 0|1
           This option controls whether clients can use this server as a
           single hop proxy. If set to 1, clients can use this server as an
           exit even if it is the only hop in the circuit. Note that most
           clients will refuse to use servers that set this option, since m=
ost
           clients have ExcludeSingleHopRelays set. (Default: 0)

       ExcludeSingleHopRelays 0|1
           This option controls whether circuits built by Tor will include
           relays with the AllowSingleHopExits flag set to true. If
           ExcludeSingleHopRelays is set to 0, these relays will be include=
d.
           Note that these relays might be at higher risk of being seized or
           observed, so they are not normally included. Also note that
           relatively few clients turn off this option, so using these rela=
ys
           might make your client stand out. (Default: 1)

So it seems like you can already experiment with that. Dunno how many exit
nodes actually enable the single hop mode though.

--=20
With respect,
Roman

--Sig_/plHRhUbaov1un34GxkJ8OQ5
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlddxEkACgkQTLKSvz+PZwjrBwCcDOLKA+m65UvrU+K5mhjux/fF
3XMAoI4FZNuRCgKuSz1RsU5pDVKwcav1
=FCXB
-----END PGP SIGNATURE-----

--Sig_/plHRhUbaov1un34GxkJ8OQ5--

--===============8246978189152357701==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

LS0gCnRvci10YWxrIG1haWxpbmcgbGlzdCAtIHRvci10YWxrQGxpc3RzLnRvcnByb2plY3Qub3Jn
ClRvIHVuc3Vic2NyaWJlIG9yIGNoYW5nZSBvdGhlciBzZXR0aW5ncyBnbyB0bwpodHRwczovL2xp
c3RzLnRvcnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby90b3ItdGFsawo=

--===============8246978189152357701==--

