Delivery-Date: Mon, 21 Jul 2014 14:51:02 -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_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,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 783781E0CFD
	for <archiver@seul.org>; Mon, 21 Jul 2014 14:50:36 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3F97730483;
	Mon, 21 Jul 2014 18:41:38 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 92D3B2FF48
 for <tor-talk@lists.torproject.org>; Mon, 21 Jul 2014 18:30:40 +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 Gbzk-EL5oNAJ for <tor-talk@lists.torproject.org>;
 Mon, 21 Jul 2014 18:30:40 +0000 (UTC)
Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com
 [IPv6:2607:f8b0:400c:c03::22e])
 (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 6FD3A28CCE
 for <tor-talk@lists.torproject.org>; Mon, 21 Jul 2014 18:30:40 +0000 (UTC)
Received: by mail-vc0-f174.google.com with SMTP id la4so12889485vcb.33
 for <tor-talk@lists.torproject.org>; Mon, 21 Jul 2014 11:30:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=WSvLBVVVV8gdk2oO2MkRQFg7lM7ZdJ95L3BrF5BUubM=;
 b=DOiPJZH0GqrIuSI2wzyw/oEIO1eOiLI5sJUP0KiCexA5QhpWAZBodUudz/lca7tA76
 iwaUocgp9RoWKPBOvPlXSoTEkryBvecrArfQN5EYFlJoLUHCVKNwE6GQOYJ53fd28Wc0
 znnsu2uTxtWn5Pmak3CsLhph3MAtNR+C4gWhqFO3zhn8V6FrIsc3CzDSyjoc2dlzjrlK
 /vDI/730fS92ppcBkZpN7AAbcxs+Mx6roLVWwqpzGKjwzqPZf0O98i3ZOhQNHOb+CgYR
 sl6aEzcz/I4+s3OgpQLXEwrivrhclcNMX5IXxFTMTZpbFMRIxY4P9BKBPe3KDaz0bBl0
 97LQ==
MIME-Version: 1.0
X-Received: by 10.52.37.81 with SMTP id w17mr3913448vdj.95.1405967436913; Mon,
 21 Jul 2014 11:30:36 -0700 (PDT)
Received: by 10.221.65.131 with HTTP; Mon, 21 Jul 2014 11:30:36 -0700 (PDT)
In-Reply-To: <dc9894e376d81c69497ed841dde8e40d@triangulum.uberspace.de>
References: <dc9894e376d81c69497ed841dde8e40d@triangulum.uberspace.de>
Date: Mon, 21 Jul 2014 14:30:36 -0400
Message-ID: <CAD2Ti29CdxnsWntXAH4VQ5_eEccQQ-U-conEUUBmgRWRwvPAJA@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] OnionCat hostname resolution?
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>

On Mon, Jul 21, 2014 at 6:55 AM, Rene Bartsch <ml@bartschnet.de> wrote:
> if OnionCat ist used, does the TOR Hidden Service name resolve/route to the
> OnionCat IPv6 address?

No, not in the clearnet sense.

Overview...
There is a one-to-one mapping between the Tor provided HS .onion address
and the onioncat provided IPv6 tun(4) interface address. You can pass
IPv6 packets between hosts over Tor as if Tor was one big IPv6/48
Layer3 network. TCP/UDP/ICMP/whatever... it's very cool.

The only way to reach the onioncat IPv6 tun(4) interface address is from
another onioncat provided IPv6 address across Tor (excepting locally
through the stack on your host, which you've hopefully firewalled as
needed). The only thing you can reach 'via the TOR HS hostname' is
the ocat daemon on 8060.

(ocat::1 <--> foo.onion:8060)  <-----> (bar.onion:8060 <--> ocat::2)

You can 'resolve' (actually, 'convert' for configuration usage) onion
and IPv6 addresses with ocat -i/-o. Onioncat takes care of that
automatically when passing traffic to and from your node.

You can also key the onions in torrc, use IPSEC, firewall, etc
if you need more control against access/spoofing.

> Is it possible to reach a server process running on
> the OnionCat IPv6-address via the TOR Hidden Service hostname?

Yes. You can use torrc HiddenServicePort to forward an onion
port to a port on your ocat IPv6 address, or ::1, or 127.0.0.1, etc.
In this case, there is no 'resolve', but it does 'route'.

user -----> (bar.onion:443 --> ocat::2:443)
-- 
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

