Delivery-Date: Thu, 23 Oct 2014 16:44:28 -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_SIGNED,
	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 383B71E0B66;
	Thu, 23 Oct 2014 16:44:27 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id CC6133110A;
	Thu, 23 Oct 2014 20:44:22 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A033731097
 for <tor-talk@lists.torproject.org>; Thu, 23 Oct 2014 20:44:18 +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 1XvWKw9LC8Yj for <tor-talk@lists.torproject.org>;
 Thu, 23 Oct 2014 20:44:18 +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 39926204FF
 for <tor-talk@lists.torproject.org>; Thu, 23 Oct 2014 20:44:14 +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;
 bh=FKFzpMcFx4I6YqoLqJUjmg/VP6bqDmbIeciTnCEvLMA=;
 b=FS/kHOojCdsIpYqW631eBytzbeQLMpCj3tUIxWWqVRhx7q6G0Gr/XgeTyDikc0ZHX5OFY0hSnRTy95Cw5vg2habp+zMEvw7d7vu4paah2cWyETTXuhGD+iLnVvQL44pgG5A1Nblp1LPkWPOsa/TS9ZwBSwevcn8qB3w81gjI0As=
Received: from 127.0.0.1 (BITMESSAGE [127.0.0.1])
 by mail.bitmessage.ch with ESMTPA ; Thu, 23 Oct 2014 22:44:05 +0200
Message-ID: <54496897.1090600@bitmessage.ch>
Date: Thu, 23 Oct 2014 20:44:07 +0000
From: Nusenu <BM-2D8wMEVgGVY76je1WXNPfo8SrpZt5yGHES@bitmessage.ch>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
Subject: [tor-talk] tor v0.2.5.x hits 'stable' repos / ControlPort auth
	behaviour change?
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>

Just a heads up in case your tor daemon does not come up after the
update as it did in my case (actually my fault).

If you use torproject's RPM repo at
https://deb.torproject.org/torproject.org/rpm/

you might realize that you are getting tor v0.2.5.x(-rc) instead of
0.2.4.x (since 0.2.5.x is probably soon the new stable).

(same is apparently true for APT repos)

One notable "side effect" from this transition is that the 0.2.5.x RPMs
take your settings from /etc/tor/torrc into account (fixes #12834).

[1] https://trac.torproject.org/projects/tor/ticket/12834


Another observation (bug?) I made after transitioning from 0.2.4.x to
0.2.5.x that I'd like to have some confirm/can't confirm options is the
following:

I use vidalia to connect to a system tor (via HashedControlPassword
authentication).

Regarding the control port I had the following two lines in my torrc:

ControlPort 9051
HashedControlPassword xxxxxxxxx

after the upgrade to tor 0.2.5.9-rc vidalia was unable to connect and
complained that tor asked for the authentication cookie - even though I
did not set CookieAuthentication. Only after explicitly setting
CookieAuthentication to 0 (which is the default anyway) vidalia was able
to connect using the password auth again.

Can anyone confirm this?





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

