Delivery-Date: Sat, 18 Oct 2014 20:17:34 -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.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	FROM_LOCAL_NOVOWEL,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 F171A1E02D2;
	Sat, 18 Oct 2014 20:17:30 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C6A4C30EF2;
	Sun, 19 Oct 2014 00:17:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B7F512E6F9
 for <tor-talk@lists.torproject.org>; Sun, 19 Oct 2014 00:17:22 +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 pAJwzl10qw23 for <tor-talk@lists.torproject.org>;
 Sun, 19 Oct 2014 00:17:22 +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 508B729D81
 for <tor-talk@lists.torproject.org>; Sun, 19 Oct 2014 00:17:21 +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:In-Reply-To:References;
 bh=bGobICS+ky86U1PLVMaDx53vz+EvD85xNh0Vh9cLw9Y=;
 b=TLfpwobiDUYc6VAFG3dcEKXq/esjnEL5tQwATGHm7dFdrHaPQcVqvMo6fGNKQl17UZQjTAcvXv1MljjguoUMHcO9MiT4vuS6iC7VmUFm/URUK68a/oJ6X++oIofdkrV0VqynQp4DBgdrYm41eiVaazcP1uS12CMJ2R57uwNjWpE=
Received: from localhost (BITMESSAGE [127.0.0.1])
 by mail.bitmessage.ch with ESMTPA ; Sun, 19 Oct 2014 02:16:32 +0200
Message-ID: <70EB6DBE-6452-43ED-A4D7-67370813E4C5@mail.bitmessage.ch>
Date: Sat, 18 Oct 2014 20:16:16 -0400
From: <BM-2cTjsegDfZQNGQWUQjSwro6jrWLC9B3MN3@bitmessage.ch>
To: tor-talk@lists.torproject.org
In-Reply-To: <mailman.6192.1413384706.22553.tor-talk@lists.torproject.org>
References: <mailman.6192.1413384706.22553.tor-talk@lists.torproject.org>
MIME-Version: 1.0
Subject: [tor-talk] firewall prompt gone in 4.0?
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>

It appears the nice firewall prompt has been removed in TBB 4.0. For
those of us who block all but a couple outgoing ports (and all the
incoming), is the only way to retain this functionality to edit the
"torrc" file with something like below for every new download?

ReachableAddresses accept *:80
ReachableAddresses accept *:443

Compared to the menu item, this seems rather inconvenient for linux
users who (quite surprisingly) don't have any well-developed means
to block outgoing traffic on a per-application basis, and resort to the
less effective, though slightly more cautious practice of just opening a
couple outgoing ports?

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

