Delivery-Date: Mon, 05 Jan 2015 10:57:23 -0500
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_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	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 4517D1E0331
	for <archiver@seul.org>; Mon,  5 Jan 2015 10:57:22 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 85DE932AE5;
	Mon,  5 Jan 2015 15:57:20 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id E6A87329F1
 for <tor-talk@lists.torproject.org>; Mon,  5 Jan 2015 15:57:16 +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 SNSi6I8I5dCD for <tor-talk@lists.torproject.org>;
 Mon,  5 Jan 2015 15:57:16 +0000 (UTC)
Received: from mail-ie0-x234.google.com (mail-ie0-x234.google.com
 [IPv6:2607:f8b0:4001:c03::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id C5C2232956
 for <tor-talk@lists.torproject.org>; Mon,  5 Jan 2015 15:57:16 +0000 (UTC)
Received: by mail-ie0-f180.google.com with SMTP id rp18so19145084iec.25
 for <tor-talk@lists.torproject.org>; Mon, 05 Jan 2015 07:57:14 -0800 (PST)
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=rXRNb5D3Qqedmizwe0lpwWsd3e4z7mp/6FipUR8k3Zg=;
 b=dtBoCkXG4xmM/3gh6dEA7AoWxXsYWlQyi0gbMnnaOdVAKoo+xp1HkmRkuSBP8+e0J2
 dLeTjNhg9bladjy6eRKGbkyb/W4JNIy2rE7TrVk2ATdBOsWHoMqb6HD6UBLQNm9WRQNo
 3DKTi8Q8UdNsItvAxLoH/pWWb86gSUVTZeO1C8Z3dCadcPgwQr7ODEWLkhlpPBxkGrg5
 Wa7gJmtVzlWNNl76u+RpUk8osgpQ+UiV1eUgOZ4DAkKVgj+o9hJeIaKAI8mLmwBqf48P
 JwZmWg/mF37fh2zKLH2trPRhG+tI7EvW2ra3roHver3FOOS0Nbqyr+U78f9mPu7Cae2N
 O9lw==
MIME-Version: 1.0
X-Received: by 10.42.235.80 with SMTP id kf16mr23914101icb.77.1420473434421;
 Mon, 05 Jan 2015 07:57:14 -0800 (PST)
Received: by 10.64.125.69 with HTTP; Mon, 5 Jan 2015 07:57:14 -0800 (PST)
Date: Mon, 5 Jan 2015 16:57:14 +0100
Message-ID: <CAB=COR7iiKtvJhkBhar=hch287R0yDsDyW=vapBZJOZ+NqnfWg@mail.gmail.com>
From: Hollow Quincy <hollow.quincy@gmail.com>
To: tor-talk@lists.torproject.org
Subject: [tor-talk] TOR issues
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 TOR community,

I spend some time to understand how TOR works. I still cannot
understand some design assumptions. Could you please help me to
understand some issues ?

1) Who store the mapping Onion_URL to real IP ? How exit node know
where to send request ?

2) How to become Exit Node ?
I understand that everyone can become normal node. If I become exit
node even for some requests I can find mapping Onion_URL to real IP.
Than IP of the page is not secret any more.

3) How the communication is encrypted between nodes ?
RSA encryption is not resistant for Man In The Middle attack. (that's
why when I connect to new SSH server I need to add public key of the
server to trusted list).
When I use TOR my request goes to Node1 and than to Node2. How can I
establish save connection with Node2, when Node1 is between us ?

4) Is there a single point of failure ?
There need to be one central place where all IPs of TOR nodes are
stored, so when I run my TOR bundle I go to this place and read node
list and send requests using it. So if this place is down (for example
because DDOS attract) new users will not be able to use TOR network.
They will not find any TOR node.

Thank you for help to understand the TOR network
-- 
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

