Delivery-Date: Thu, 25 Aug 2016 07:19:26 -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 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 [138.201.14.202])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 9A45A1E02E7;
	Thu, 25 Aug 2016 07:19:24 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 2051CE04F2;
	Thu, 25 Aug 2016 11:19:00 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 355AEE04CE
 for <tor-talk@lists.torproject.org>; Thu, 25 Aug 2016 11:18:55 +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 a1QufZFpKJzT for <tor-talk@lists.torproject.org>;
 Thu, 25 Aug 2016 11:18:55 +0000 (UTC)
Received: from avatar.getfoxyproxy.org (avatar.getfoxyproxy.org
 [45.79.173.108])
 by eugeni.torproject.org (Postfix) with ESMTP id E08A3E046C
 for <tor-talk@lists.torproject.org>; Thu, 25 Aug 2016 11:18:54 +0000 (UTC)
Received: from [127.0.0.1] (unknown [93.113.36.242])
 (Authenticated sender: georg@getfoxyproxy.org)
 by avatar.getfoxyproxy.org (Postfix) with ESMTPSA id 75B2D41DA
 for <tor-talk@lists.torproject.org>; Thu, 25 Aug 2016 11:18:51 +0000 (UTC)
To: tor-talk@lists.torproject.org
References: <ee27996569ad0b35833cba1036fc9b08@posteo.de>
From: Georg Koppen <gk@torproject.org>
Message-ID: <1c6b85d5-ddb8-2888-2258-8a87855b5bbf@torproject.org>
Date: Thu, 25 Aug 2016 11:18:00 +0000
MIME-Version: 1.0
In-Reply-To: <ee27996569ad0b35833cba1036fc9b08@posteo.de>
X-Content-Filtered-By: Mailman/MimeDel 2.1.18
Subject: Re: [tor-talk] Tor Browser Bundle update mechanism for Unix
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.18
Precedence: list
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>
Reply-To: tor-talk@lists.torproject.org
Content-Type: multipart/mixed; boundary="===============1598133295974791340=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--===============1598133295974791340==
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature";
 boundary="2Ht95tBCol36wl41tcfG9h0hUBUU2cc1p"

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--2Ht95tBCol36wl41tcfG9h0hUBUU2cc1p
From: Georg Koppen <gk@torproject.org>
To: tor-talk@lists.torproject.org
Message-ID: <1c6b85d5-ddb8-2888-2258-8a87855b5bbf@torproject.org>
Subject: Re: [tor-talk] Tor Browser Bundle update mechanism for Unix
References: <ee27996569ad0b35833cba1036fc9b08@posteo.de>
In-Reply-To: <ee27996569ad0b35833cba1036fc9b08@posteo.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

anonymous.coward@posteo.de:
> Dear list,
>=20
> can someone explain how the TBB update mechanism works precisely with
> Unix operating systems?
>=20
> Especially I=C2=B4d like to know, does it use a shell script for updati=
ng the
> TBB?
> If yes, will the shell script be downloaded first or is it already
> existing?
>=20
> Is the binary Browser/updater the program that processes the update?
>=20
> I=C2=B4m asking, because I use Mandatory Access Control to confine the
> browser bundle and need to know how the update mechanism may require to=

> access the TBB directory and files.

We are basically using the update mechanism of Firefox but point it to
our own servers. See: https://wiki.mozilla.org/Software_Update and the
links in the link list on that site to get an overview of how the system
is working.

Georg

> Thanks
>=20



--2Ht95tBCol36wl41tcfG9h0hUBUU2cc1p
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXvtQGAAoJEKpgLMAMJXz3ppMQAK+5S2lMZSy/85LbwRw0vC97
3+HsXLhMxk4xFBATgKSa7Y2/fglgAsFKfgZoDTBh4qlWplCKd+JMjtav5Ms0HelE
63eySdhqOUI1Ct8FZgFqyRby/K75X+5yA64KildaDl9WIgfakA5n+k5ry5hWufvx
RzfA2nOOSwgExHZNxd/C+0XbNlIphqEB9KQfrLwRK52bcMVv2AalAeG2arV28vKb
e2FbWiBy+33SOdUiTmxCowxHCDrt9rB3l7KDL8d452dQkUpfx9zGYM1Na+FeVvnW
/iHS8hVc/3U1oO6idAgevy3CDxHM7ukVsahlikRtsyKZIP3xUHIDiAGYvJA1WxrL
YndgRQRl28l7Y6zuvygsjmEys6yLRvfA3El4sOI28Ei9OMW4U5n9VK0rE3j0moY/
/FHypRhYyYfBLPP6ncAi7174+UsC/Ac+uqu5ckNWJvOWPsbM5RFdOg2KGm7BU6r1
YscA/fo0efMdYx2UwmDq1LYGF7vDJB56teA0X/XF6deUxDfO/siL7Xnm348tpMi6
lY6grhnyq7DH98MdWaQDXWFwyIG9dnjn94vD3e3KZ/OzKLSVxOQO/0j2BQsd944q
93JpEHWgKtRo4kurmL4EIU1CEsGi/0yUAZjfQWSt1THwMOFGPnIoUnBiSkD+2eTU
9Iy+r8Urq0QAelHyYYJv
=rJXY
-----END PGP SIGNATURE-----

--2Ht95tBCol36wl41tcfG9h0hUBUU2cc1p--

--===============1598133295974791340==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

LS0gCnRvci10YWxrIG1haWxpbmcgbGlzdCAtIHRvci10YWxrQGxpc3RzLnRvcnByb2plY3Qub3Jn
ClRvIHVuc3Vic2NyaWJlIG9yIGNoYW5nZSBvdGhlciBzZXR0aW5ncyBnbyB0bwpodHRwczovL2xp
c3RzLnRvcnByb2plY3Qub3JnL2NnaS1iaW4vbWFpbG1hbi9saXN0aW5mby90b3ItdGFsawo=

--===============1598133295974791340==--

