Delivery-Date: Sat, 06 Jun 2015 08:00:01 -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=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	DKIM_SIGNED,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,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 [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id D9E3E1E0478;
	Sat,  6 Jun 2015 07:59:58 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 79F1B3582E;
	Sat,  6 Jun 2015 11:59:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id E3E1735826
 for <tor-talk@lists.torproject.org>; Sat,  6 Jun 2015 11:59:49 +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 wU3G1_Jv7Cs9 for <tor-talk@lists.torproject.org>;
 Sat,  6 Jun 2015 11:59:49 +0000 (UTC)
Received: from smtp7.openmailbox.org (smtp7.openmailbox.org [62.4.1.41])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 9AF863581F
 for <tor-talk@lists.torproject.org>; Sat,  6 Jun 2015 11:59:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mail2.openmailbox.org (Postfix) with ESMTP id 21B2220015F
 for <tor-talk@lists.torproject.org>; Sat,  6 Jun 2015 13:59:45 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=openmailbox.org;
 h=content-transfer-encoding:content-type:content-type:subject
 :subject:mime-version:from:from:date:date:message-id:received;
 s=openmailbox; t=1433591983; bh=4mwUtl4pJ1U51zvYQNU6jBh1l8ucOIW
 990jhLHxOHq0=; b=uWKCdpZhTLjH4h8d2hL/1xdUyAxUa0AFmQfxASHtGm8kelr
 11WDbq+oC9KVp8MVXquR/Z2BG2BZKhjCw5XkZvJayTitTTBFX489YgKsYEfLcOnx
 aIZh0NmJUPuq9Q2bYI5TL6OgTqZEEyx/hSc2B5mJqm1izX2FKSQ3/040r1gA=
X-Virus-Scanned: amavisd-new at openmailbox.org
Received: from mail2.openmailbox.org ([62.4.1.33])
 by localhost (mail.openmailbox.org [127.0.0.1]) (amavisd-new, port 10026)
 with ESMTP id 5q2zatOg_1Q8 for <tor-talk@lists.torproject.org>;
 Sat,  6 Jun 2015 13:59:43 +0200 (CEST)
Message-ID: <5572E0A9.6080003@openmailbox.org>
Date: Sat, 06 Jun 2015 11:59:37 +0000
From: nusenu <nusenu@openmailbox.org>
MIME-Version: 1.0
To: "tor-talk@lists.torproject.org" <tor-talk@lists.torproject.org>
Subject: [tor-talk] understanding client side enforced families
	('NodeFamily' parameter)
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,

I'd like to properly understand the implications of tor's 'NodeFamily'
config option and if there is a DirAuth enforcable config option
similar to this client side option (something I did not find in the
man page yet).

names convention I'm using in this email

* undeclared family
a confirmed (by the operator) or likely group of relays operated by a
single entity or group

* declared family
a family defined by the list of fingerprints a given relay publishes
in the family line of its descriptor (for simplicity we assume there
are only fingerprints and ignore everything else).

* effective family
the overlapping list of fingerprints between declared family and
mutually agreed relationships. The effective family might be smaller
(in terms of element count) or equal but never bigger than the
declared family.

* client family
family defined by the list of fingerprints configured on a tor client
via 'NodeFamily'

* real effective family
the set of fingerprints considered to be in family after evaluating
effective families and NodeFamily torrc config lines


I assume a tor client becomes more unique as soon as he uses the
NodeFamily option but this "uniqueness" is expected to be hardly
measurable as long as NodeFamily is used reasonably (and the risks of
using multiple relays from a given undeclared family are expected to
be greater than this newly introduced uniqueness).

Questions

- - Is it possible to (accidentally) reduce the size (by element count)
of a real effective family by using NodeFamily or is the real
effective family size always the bigger of size(effective family) and
size(client family)?

Example:
effective family is: A, B, C, D
NodeFamily (accidentally) is: A, B

What is the resulting real effective family?
1) real eff. family = A, B, C, D
or
2) 	real eff. fam1 = A, B;
	rea eff. fam2 = C, D;


- - Is it possible to (accidentally) create real effective families by
using NodeFamily that are bigger than size(effective family) or
size(client family)? (That implies that client families have the power
to link multiple families into one even though the client family only
lists a subset of thouse.)

Example:
eff. family1 = A, B, C
eff. family2 = B, C, D

A and D are not in the same family, is this still true after setting
NodeFamily: B, C
or
NodeFamily: A, B


thanks,
nusenu





-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJVcuCpAAoJEFv7XvVCELh0pYwP/RkYY/8iYGdp0NWezmxZo5Fh
LBUrbQ2JvHI3xtk74+uHHMorO4w6JDRt4+xeXqSow9jZh2gvMBwTeQEGr9PfOujD
oujNm9zE/u7jwv4F3t9fwcdIuLVqFfTuWMLg4HhYD6theTjkVmevSJmbvPSlGKE2
NFGYhqyQSssvgyJOieBXVVeXYWtq8Iqai3yQtHD7gCmgqGTDhBuLdNi8tBu33pD3
JASgdu+uEaYr1J2zSRnDmi4VCQPCT7nn+GGi73X5tQf47OdLaq0f/M71HkslUIoJ
eUJPAMwx1nTLV5geSc7K1+TLAwN0n97ZTYfCi/VugsndUvnOIi7+feEPrNde68BI
ST7nJK04c4EhV0u1LplecOWH7f6SRT/WvdwiNIGbU94UFYORlW9okJfvAbUEzykK
YVdh8qieRpYfsxJ3Ce9ClsZKS48p3pMUKopE7dCPiQcl5N5u26BgPKfAMtwN5ans
38xW7n0YshyeEM0mhj3bpKqpA9EAaXohXT1+P5kkBtrMZspLgGDR86QVTwQIZyb7
gGyEtS3QziClvou0GC6OtEDs+7l3zU7K8nQGyAGlZbt8cKRXCot8MPVsDrpWR944
Pjl8eeBC/oMVjFRya0LpXxJ3CKNnOVjlIL819ziQ+myYAyPocd0bF4hb5ER2318v
Wx3wmKKQUAmP1N5zIQIP
=KOMO
-----END PGP SIGNATURE-----
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

