Delivery-Date: Fri, 20 Nov 2015 20:21:33 -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.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
	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 AB8F41E00C4;
	Fri, 20 Nov 2015 20:21:31 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E7E73375E5;
	Sat, 21 Nov 2015 01:21:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 918A7375CD
 for <tor-talk@lists.torproject.org>; Sat, 21 Nov 2015 01:21:22 +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 DOJ3U7Y71G7n for <tor-talk@lists.torproject.org>;
 Sat, 21 Nov 2015 01:21:22 +0000 (UTC)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com
 [IPv6:2607:f8b0:4001:c06::230])
 (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 7A315375B0
 for <tor-talk@lists.torproject.org>; Sat, 21 Nov 2015 01:21:19 +0000 (UTC)
Received: by ioc74 with SMTP id 74so140673739ioc.2
 for <tor-talk@lists.torproject.org>; Fri, 20 Nov 2015 17:21:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:from:date:message-id:subject:to:content-type;
 bh=zruPVDGCcmVDQSBQ1XPcsf+O+ghzBKRnLGcNc0TEeds=;
 b=I3XpUpunEMRevQX48Nejxjrcq0WsY/VsdOlde/2OsFtHfLgiY0fNkNCo34gf406T+9
 4BspGNcI6zDll/HYcBhtREItpm22x57KJk3/BIaZnRWHj1V4tHKERzHTcu8Vjbywjwod
 s9fE3boHeIxqez+hXQRocfA6yfLsgz5AKzmc3XVYAJssdUc1zG++w4l0PiuSp6hhdAE9
 bd9y5tv2KMMdDsFIaYiZq0U80KV/yPCcG/Pvj5/PeQQXhOlsGol2B9zGvnZV5IOFcdHM
 MLYv3JlK/h8dA2YrEalB8UZ5bL7mXtBjCbLIxptia7cMxcIkC5jqSyBtQ9IFuo91WuZE
 FW+w==
X-Received: by 10.107.164.71 with SMTP id n68mr16658823ioe.162.1448068877259; 
 Fri, 20 Nov 2015 17:21:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.130.224 with HTTP; Fri, 20 Nov 2015 17:20:57 -0800 (PST)
From: Abhishek Singh <abhishek.singh.kumar@gmail.com>
Date: Sat, 21 Nov 2015 02:20:57 +0100
Message-ID: <CANm7j6ODyNhar15S-eAVkcss2B+xcA15wCkKcqUkLsXh0LHd=Q@mail.gmail.com>
To: tor-talk@lists.torproject.org
Subject: [tor-talk] INTRODUCE2 cells are not forwarded by introduction points
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,

I am encountering a significant number of failures in establishing
circuits to hidden services. Client-Rendezvous-Server circuit
construction fails because a hidden service's introduction point does
not forward INTRODUCE2 cells to the origin of the hidden service. I
observe 'rend_client_introduction_acked()' in the logs on the
client-side but there is no corresponding
'rend_service_receive_introduction()' in the logs on the server-side.
In this time period the server considers HSSI circuits to the
introduction points to be working as expected and these circuits are
not torn down.

These cells can be dropped by an intermediate node in the HSSI
circuit. However, this is not the this case as the same behavior was
observed when server was setup using 1-hop circuits for HSSI.

Is this behavior of introduction points normal (because of high load)?
Or, is it the case that these introduction points are exhibiting
malicious behavior?

Thanks,
Abhishek
-- 
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

