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

[Kyle Williams]

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 at wolschon.biz>
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-----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20080520/0c8824b8/attachment.htm>