Delivery-Date: Tue, 15 Mar 2016 12:18:33 -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,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY 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 07DA01E093F;
	Tue, 15 Mar 2016 12:18:32 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C9193392D5;
	Tue, 15 Mar 2016 16:18:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 0AC6B38893
 for <tor-talk@lists.torproject.org>; Tue, 15 Mar 2016 16:18:23 +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 XanK5rWA4lZc for <tor-talk@lists.torproject.org>;
 Tue, 15 Mar 2016 16:18:22 +0000 (UTC)
Received: from paulo.mayfirst.org (paulo.mayfirst.org [209.234.253.240])
 (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 D8A0736E8D
 for <tor-talk@lists.torproject.org>; Tue, 15 Mar 2016 16:18:22 +0000 (UTC)
Received: from paulo.mayfirst.org (unknown [127.0.0.1])
 by paulo.mayfirst.org (Postfix) with ESMTP id 337C63F3C
 for <tor-talk@lists.torproject.org>; Tue, 15 Mar 2016 12:18:20 -0400 (EDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender:
 nathanfreitas@paulo.mayfirst.org) with ESMTPSA id 1E0813F16
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44])
 by mailauth.nyi.internal (Postfix) with ESMTP id DEF4821058
 for <tor-talk@lists.torproject.org>; Tue, 15 Mar 2016 12:18:19 -0400 (EDT)
Received: from web4 ([10.202.2.214])
 by compute4.internal (MEProxy); Tue, 15 Mar 2016 12:18:19 -0400
Received: by web4.nyi.internal (Postfix, from userid 99)
 id BD8511080A0; Tue, 15 Mar 2016 12:18:19 -0400 (EDT)
Message-Id: <1458058699.1184304.549907010.00BD0857@webmail.messagingengine.com>
X-Sasl-Enc: woZjQ8EaUx0X7/YpPhXJABFfXiSsvNFMlRRdyna71o3U 1458058699
From: Nathan Freitas <nathan@freitas.net>
To: tor-talk@lists.torproject.org
MIME-Version: 1.0
X-Mailer: MessagingEngine.com Webmail Interface - ajax-872772a7
Date: Tue, 15 Mar 2016 12:18:19 -0400
In-Reply-To: <512753.0def7e0aa8739be7298cde20bc7192b1749282c4@popretr.messagingengine.com>
References: <1456326910.1665396.530598386.6C05E63A@webmail.messagingengine.com>
 <512753.0def7e0aa8739be7298cde20bc7192b1749282c4@popretr.messagingengine.com>
 <56E5CDCA.9060901@bitmessage.ch>
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: Re: [tor-talk] Fwd: Orbot v15.1.2 released
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 Sun, Mar 13, 2016, at 04:30 PM, Dash Four wrote:
> I was finally able to test the newest version (below) with my set up (I
> use customised firewall/transproxy settings and a vpn - all outside
> orbot). 
> The good news is that version now works with no major problems, though I
> still found a couple of issues:

Glad to hear.

> 1. Why is it that the app upgrade wipes out the entire app_bin directory?

We hadn't considered that people would put their own files into that
directory. When we upgrade, we like to ensure it is in a clean state. We
can consider instead deleting files one by one.

> up-to-date geoip files (not the ones provided with orbot).

Could you provide these in a pull request or via a safe download link so
we can upgrade Orbot for everyone?
 
> 2. My custom settings had a separate GeoIP statements which were added by
> orbot. That's wrong. Either leave my torrc.custom file alone and don't
> mess with it, 
> or properly replace the statements used in that file.

Right. We didn't consider people would use the torrc to modify values
that Orbot itself manages. Are you writing your own torrc.custom on
disk, or adding your configuration to the field in Orbot settings?

> 3. How can I compile, or at least obtain a tor binary independently of
> the orbot installation? The reason I ask this is because the tor binary
> provided with the 
> latest version is 0.2.7.5 which is not even the latest stable, let alone
> the one I wish to use (0.2.8.0-alpha).

It takes time for us to test tor binaries on Android to ensure there are
no unintended issues with performance, battery life, memory usage, etc.
It isn't automatic.

That said, you are free to compile it yourself. All of the information
is on the code repo:
https://gitweb.torproject.org/orbot.git/tree/BUILD
https://gitweb.torproject.org/orbot.git/tree/external/Makefile

That said, we should be getting to the latest tor RC/stable soon.
 
> 4. Minor nitpick - the notification icon provided with orbot is bloody
> hideous! It looks like a circled blob and you hardly notice the arrows
> when orbot is 
> used. Can you not provide something like the onion on torproject.org, but
> with two vertical arrows (similar to the wifi notification icon)?

Bloody hideous? It is just a small version of the larger icon we use on
the app screen and the icon. If you shrink down any of the various
"onion" graphics, none of them look very good. We'll see if we can
recruit an icon designer to come up with something better, but always
happy again to have a pull request.

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

