Delivery-Date: Thu, 30 Oct 2014 14:23:33 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID 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 D375F1E0B0E;
	Thu, 30 Oct 2014 14:23:31 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 34808311E1;
	Thu, 30 Oct 2014 18:23:28 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A1CE231005
 for <tor-talk@lists.torproject.org>; Thu, 30 Oct 2014 18:23:25 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 5yo2f1yMZwVT for <tor-talk@lists.torproject.org>;
 Thu, 30 Oct 2014 18:23:25 +0000 (UTC)
Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252])
 (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 3E19630F01
 for <tor-talk@lists.torproject.org>; Thu, 30 Oct 2014 18:23:25 +0000 (UTC)
dkim-signature: v=1; a=rsa-sha256; d=bitmessage.ch; s=mail;
 c=relaxed/relaxed; q=dns/txt;
 h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type:Content-Transfer-Encoding;
 bh=+55jDZCKxQTVdYCjSq6R2jCRn6uMhnMska/lSN7HWiE=;
 b=izLPjJh1x2TugHGOiugYfTEmzH9rgW03D/KQqinK2pMO9WLpxKqhu6zWJmL1ygDUGm6wS+r71MxrLk4+DWBLTU8EojOboTXDzuAm5tMXOvPiTZrMF3yHWQ8yVwmK1kBK6T25+OcRowyqVP8EICBcEDHeWlgQiCHtdUFx6JUe7SA=
Received: from bitmailendavkbec.onion (BITMESSAGE [127.0.0.1])
 by mail.bitmessage.ch with ESMTPA ; Thu, 30 Oct 2014 19:22:21 +0100
X-Squirrel-UserHash: BiRDVQY7AmxBcHdjACEbPlZaKU1AdAJlCg4FFyk7NmtVSglQMikMDhEDFl1DWVZQagoG
X-Squirrel-FromHash: cw9eV1VeQx8=
Message-ID: <a06cb37688824cd1b4472ff571155c90.squirrel@bitmailendavkbec.onion>
Date: Thu, 30 Oct 2014 11:22:21 -0700
From: BM-2cUqBqHFVDHuY34ZcpL3PNgkpLUEEer8ev@bitmessage.ch
To: tor-talk@lists.torproject.org
User-Agent: SquirrelMail/1.4.22
MIME-Version: 1.0
X-Priority: 3 (Normal)
Importance: Normal
Subject: [tor-talk] Questions about crypto used in TAP/Ntor
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>

Dear experts,

Want to clarify some things:

1. The fignerprint of a Tor relay which is advertised in the direcotry
data is a SHA1 sum of which key? Sice now a relay has a secret onion key
and a secret key for Ntor.

2. The fingerprint (since it's a hash sum of the key) is what strengths
encryption between relays or clients and relays, kind of like a CA in SSL?
That is why the directory authorities sign the list of fingereprints - is
this correct?

3. How strong is Ntor compared to TAP? As I can see in latest Tor version
now clients prefer Ntor by default - are there any plans to deprecate TAP
in teh future?

4. The fingerprint is a SHA1 hash, as described in the papers. Any plans
to move in the immediate future to a stronger hash algorithm, like SHA256?


-- 
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

