Delivery-Date: Mon, 08 Feb 2016 04:13:07 -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_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,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 0E7701E0A69;
	Mon,  8 Feb 2016 04:13:05 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1B32E39413;
	Mon,  8 Feb 2016 09:12:59 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id F1F18393ED
 for <tor-talk@lists.torproject.org>; Mon,  8 Feb 2016 09:12:54 +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 glCpJT6H_p2R for <tor-talk@lists.torproject.org>;
 Mon,  8 Feb 2016 09:12:54 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id D17B2393EA
 for <tor-talk@lists.torproject.org>; Mon,  8 Feb 2016 09:12:54 +0000 (UTC)
Received: from piha.riseup.net (unknown [10.0.1.163])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 211FB1A1F15
 for <tor-talk@lists.torproject.org>; Mon,  8 Feb 2016 09:12:52 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1454922772; bh=hobaON5EDk7Kvp8qtuPGfwlOEucbhL/3yUWojS2DiwU=;
 h=Subject:To:References:From:Date:In-Reply-To:From;
 b=O9MdLvXvcITKlHEnr1K6yLF7T+VaRK5VmnXoS/FsQALO1N9LUCXGg5xt7sforw1GU
 8lL0nbfuxWvLelvTUBjb1CLrB6ZzK4z1S7+Ix5ZOLNYhHeXfaIFO6EgWngwlmueUtI
 q8wHE0yUyhk6WmvN7mu8uQzF9D2ZPZv1VaGc+d+s=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id E31441C005E
To: tor-talk@lists.torproject.org
References: <56B6971A.9070509@riseup.net> <56B853A5.2030402@torproject.org>
From: Mirimir <mirimir@riseup.net>
Message-ID: <56B85C0D.8070909@riseup.net>
Date: Mon, 8 Feb 2016 02:12:45 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <56B853A5.2030402@torproject.org>
X-Virus-Scanned: clamav-milter 0.98.7 at mx1.riseup.net
X-Virus-Status: Clean
Subject: Re: [tor-talk] automatic Tor browser updates
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 02/08/2016 01:36 AM, Georg Koppen wrote:
> Mirimir:
>> When automatically updating, does Tor browser check GPG signatures of
>> downloaded updates before installing them?
> 
> The update files are not using GPG signatures (see:
> https://wiki.mozilla.org/Software_Update:MAR for detailed information
> about the MAR file format). They are signed, though, and the updater
> refuses to install the update if the signature is non-existing or wrong.
> 
> Georg

Thank you.

For those who wish to update manually, is it sufficient to toggle
app.update.auto in about:config to false?
-- 
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

