Delivery-Date: Sun, 31 Jan 2016 17:13:36 -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.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	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 6DC801E069A;
	Sun, 31 Jan 2016 17:13:34 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 337AD38D52;
	Sun, 31 Jan 2016 22:13:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 6A22538AE0
 for <tor-talk@lists.torproject.org>; Sun, 31 Jan 2016 22:13:25 +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 GVOBoA40-oOo for <tor-talk@lists.torproject.org>;
 Sun, 31 Jan 2016 22:13:25 +0000 (UTC)
Received: from cock.li (cock.li [185.100.85.212])
 by eugeni.torproject.org (Postfix) with ESMTP id 33E5F21511
 for <tor-talk@lists.torproject.org>; Sun, 31 Jan 2016 22:13:25 +0000 (UTC)
X-Greylist: delayed 2399 seconds by postgrey-1.34 at eugeni;
 Sun, 31 Jan 2016 22:13:25 UTC
To: tor-talk@lists.torproject.org
References: <54D23891.3040409@nirgal.com>
From: "ncl@cock.li" <ncl@cock.li>
Message-ID: <56AE74A2.40602@cock.li>
Date: Sun, 31 Jan 2016 20:54:58 +0000
MIME-Version: 1.0
In-Reply-To: <54D23891.3040409@nirgal.com>
Subject: Re: [tor-talk] How to protect apache local-restricted from secret
 service access?
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>

This is/was also being discussed at
https://lists.torproject.org/pipermail/tor-onions/2016-January/000026.html

Suggestions so far are "a2dismod status" as you said, or as a more
general solution, binding the onion service to an address other than
127.0.0.1.
-- 
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

