[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: Auto-Update -Feature - Was: Draft schedule for Tor 0.2.1.x.

To: or-dev@xxxxxxxxxxxxx
Subject: Re: Auto-Update -Feature - Was: Draft schedule for Tor 0.2.1.x.
From: "Kyle Williams" <kyle.kwilliams@xxxxxxxxx>
Date: Tue, 20 May 2008 10:16:24 -0700
Cc: "Nick Mathewson" <nickm@xxxxxxxxxxxxx>
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-dev-outgoing@xxxxxxxx
Delivered-to: or-dev@xxxxxxxx
Delivery-date: Tue, 20 May 2008 13:16:31 -0400
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; bh=ghfkgATAbuvafEvdnw7oNxMOrjH9otAgaITnpZSnBiw=; b=CU5soCUw0Bz0n8D6AYRPrj79c0m1FUpbsMCxk3uBcNiJmVu7uKsAQoPmgE2S54aWE3G6zfhwdqgZVcfAUE82fVJCy1KcE3W1/QFnbLJnuj7yBBZDVnCKNEtxTcWCbKcyiSa3C7o4+3X0ASDoAnRqSm/Lbm7xCCcGi7TRNH9m0WY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=UFjpIK9GOc4iZu/5LNsipDVKnIoBOw6isoCe1yQ9+JzFzN/mVCgRiGj+Ky9mTPpAATr3JvDRF2fLtN1Y8u4poXOZG09dl0t+3qqD51CDe4vFnXEJ2tWBTDEj+yfdWcFOKNt4Z7eeSqzzinIXquP0HqvZxNpgd0MxGszHUHpcnWM=
In-reply-to: <483266B3.6050903@xxxxxxxxxxxx>
References: <20080519195631.GA27864@xxxxxxxxxxxxxx> <21f144250805191519t488998b6obff3117dc81ac764@xxxxxxxxxxxxxx> <483266B3.6050903@xxxxxxxxxxxx>
Reply-to: or-dev@xxxxxxxxxxxxx
Sender: owner-or-dev@xxxxxxxxxxxxx

Hello Marcus,

Sorry for not making this more clear. Thank you for bringing up that point, which I will address in a moment.

I was referring to the 200,000+ users that are using Tor as a client. Most of the users are using Tor on a desktop or laptop.
I would put this 'in your face' alert on the shoulders of Vidalia, since it's what most people use to control Tor.

So, back to the head-less server sitting in a data center. Tor already has a recommended versions that is sent out by the Directory Authorities.
Perhaps a LATEST_STABLE parameter could be sent out, and upon receiving an update for LATEST_STABLE, one's own Tor instance could automatically update itself. Which brings us to the next question, how do we make this controllable by the operator. I purpose a AutoUpdate flag in the torrc.

AutoUpdate 1 means update to the LATEST_STABLE
AutoUpdate 0 means don't automatically update to LATEST_STABLE

Which one should be the default? I bet there would be a lot of debate about this. I say AutoUpdate 1 should be the default.

Both options would of course create the appropriate logs messages in Tor's log.
I'm sure there are a couple of technical aspect's of this I haven't considered yet, but the general idea isn't a new one and has been done before with lots of software products available today.

- Kyle

On Mon, May 19, 2008 at 10:50 PM, Marcus Wolschon <marcus@xxxxxxxxxxxx> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Kyle,

so what is your proposal exactly?
How do you suppose a background-service
on a very possibly headless and unattended
machine in a data-center should issue such
a message to the administrator?

Marcus

Kyle Williams schrieb:
| Nick,
|
| I have a suggestion. Automatic updates.
| Here is my reason as to why I feel this is probably the most important
| feature you need to implement.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIMmazf1hPnk3Z0cQRAvCVAKCIB6B3m/UmQfg0liObSLElA0uBDgCg1fJe
M6e6o7CzN1oxPBEEUM2cXak=
=lkkw
-----END PGP SIGNATURE-----

Follow-Ups:
- Re: Auto-Update -Feature - Was: Draft schedule for Tor 0.2.1.x.
  - From: phobos

References:
- Draft schedule for Tor 0.2.1.x.
  - From: Nick Mathewson
- Re: Draft schedule for Tor 0.2.1.x.
  - From: Kyle Williams
- Auto-Update -Feature - Was: Draft schedule for Tor 0.2.1.x.
  - From: Marcus Wolschon

Prev by Author: Re: Draft schedule for Tor 0.2.1.x.
Next by Author: Fingerprint is marked rejected
Previous by thread: Auto-Update -Feature - Was: Draft schedule for Tor 0.2.1.x.
Next by thread: Re: Auto-Update -Feature - Was: Draft schedule for Tor 0.2.1.x.
Index(es):
- Author
- Thread