Delivery-Date: Tue, 10 Mar 2015 01:34:22 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,
	URIBL_BLOCKED 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 B576F1E0BF3
	for <archiver@seul.org>; Tue, 10 Mar 2015 01:34:20 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 152B8343F0;
	Tue, 10 Mar 2015 05:34:17 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 80EDC343EC
 for <tor-talk@lists.torproject.org>; Tue, 10 Mar 2015 05:34:13 +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 fus47FJtI5uT for <tor-talk@lists.torproject.org>;
 Tue, 10 Mar 2015 05:34:13 +0000 (UTC)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com
 [IPv6:2607:f8b0:4003:c01::235])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 5A53E343E6
 for <tor-talk@lists.torproject.org>; Tue, 10 Mar 2015 05:34:13 +0000 (UTC)
Received: by obcvb8 with SMTP id vb8so34513170obc.0
 for <tor-talk@lists.torproject.org>; Mon, 09 Mar 2015 22:34:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:date:message-id:subject:from:to:content-type;
 bh=ghRAcPZCbI6YbItaFMo19rpVWzGKiAoykV4q5nr35hw=;
 b=UVKTGQcl+/xKr5VqRiz33DRPldARlTuMeQa97vHYqxqgCEZbzcKYQ2tXw7PyLqSL/m
 GVZ/D2YOb1/R4u220D365ieEHYqMSRU0MCyhGYylOBoDnsmysAj8bMITRZ02iib5GRL/
 RMx/MjiUkE10SLTPjrNaph2+31yTwBTQrRj5HeincHOjJ8CpEYTZga2qj/SWops1BC62
 k+GMhcNm9Pg4BpQjiaPGEgSCmuLrzOpY1Wzrxl7ZgNrqC7ZxTR0VzG9BuGS2UTpa8UI1
 PWV43vnWZkIaUHXCM17esaanfSFPvbugHFNratEl003K++AmeEftbWeM9NJ00v1EDdmn
 cXqw==
MIME-Version: 1.0
X-Received: by 10.60.48.98 with SMTP id k2mr24532595oen.49.1425965650921; Mon,
 09 Mar 2015 22:34:10 -0700 (PDT)
Received: by 10.202.64.5 with HTTP; Mon, 9 Mar 2015 22:34:10 -0700 (PDT)
Date: Tue, 10 Mar 2015 14:34:10 +0900
Message-ID: <CALRdebzY9uXK4=oFmny8X_B_VTb+6-on7gT9RUdVp5WbcjZkeg@mail.gmail.com>
From: Anonymous Kyoto <anonymous.kyoto@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [tor-talk] What is the different between cached-microdescs,
 cached-microdesc-consensus and cached-microdescs.new?
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>

Hi all,
I just have a look at ~/Tor Browser\Browser\TorBrowser\Data\Tor and see the
above mentioned 3 files. I don't really know how they are different in both
"content" and "role".

Which file is used to build circuit by Client?
Which File is used to checked "the validity of recent-possessing network
document"?

TO the best of my knowledge, client check whether there are any
downloadable descriptors (currently every 10 seconds according to
dir-spec.txt). So could anyone please explain or give me a hint of how the
client really "CHECK" that?
For example:
in the cached-microdesc-consensus file contains a descriptor
____
r PDrelay1 AAFJ5u9xAqrKlpDW6N0pMhJLlKs 2015-03-09 10:53:09 95.215.44.189
8080 0
m CPe8dnlRHAy8MxrtSS1QTQzlZl8fesAIahWCwUz5W5U
s Fast Running Stable Valid
v Tor 0.2.5.10
w Bandwidth=404
____

in the cached-microdescs file contains this:
____
onion-key
-----BEGIN RSA PUBLIC KEY-----
MIGJAoGBALx34lHj8UR4uM6uckNlHYZfVi0YsVhOBZ7H0MUbCoe5YMmMCSVLxyaE
lNZMQj5RV+ezKUB0TOW7XjJwoL5jq+mn1UGjpaH+ANKZPPpg6kelpxGShdVmxIEI
vCxLPM40mAypKKzEoDlYqzv1KcCXzKH3d/KOPRKXu+bMCg6KGxh9AgMBAAE=
-----END RSA PUBLIC KEY-----
ntor-onion-key 8VFLG7Hs7Phh8vdNCZDOmHUfVu8wa75UgSbj7A+wFig=
a [2a02:7aa0:1619::9847:f57c]:8080
family $2224E7AF8101885850EC7F2F9EB99F823E8014BE
$5B8706EB8B9130F791B39346765B3978EB657E07
$63084BB607DD0C6E74021422FEB691392208B330
$DCD19D25D6A0DFEB63ECA9A02033B3B3181BCFFC
id rsa1024 AAFJ5u9xAqrKlpDW6N0pMhJLlKs
@last-listed 2015-03-09 03:46:20
____

So which value Client will parse and send to Directory Mirrors to Check if
a descriptor is still valid or invalid in this case, is that the
"AAFJ5u9xAqrKlpDW6N0pMhJLlKs", cos I can only find this is the only common
value between two files?
Will Client have to send all of "that-value" of all recent possessing
descriptors to Mirrors to test? If yes, how the Mirrors will handle those
values?

Thank you for reading my question, and please correct me if I said
something wrong.
Yours Sincerely.
-- 
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

