Hello Marcus,<br><br>Sorry for not making this more clear. Thank you for bringing up that point, which I will address in a moment.<br><br>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.<br>
I would put this 'in your face' alert on the shoulders of Vidalia, since it's what most people use to control Tor.<br><br>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. <br>
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. <br>
<br>AutoUpdate 1 means update to the LATEST_STABLE<br>AutoUpdate 0 means don't automatically update to LATEST_STABLE<br><br>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.<br>
<br>Both options would of course create the appropriate logs messages in Tor's log.<br>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.<br>
<br>- Kyle<br><br><br><div class="gmail_quote">On Mon, May 19, 2008 at 10:50 PM, Marcus Wolschon <<a href="mailto:marcus@wolschon.biz">marcus@wolschon.biz</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
<br>
<br>
Hello Kyle,<br>
<br>
so what is your proposal exactly?<br>
How do you suppose a background-service<br>
on a very possibly headless and unattended<br>
machine in a data-center should issue such<br>
a message to the administrator?<br>
<br>
Marcus<br>
<br>
Kyle Williams schrieb:<br>
| Nick,<br>
|<br>
| I have a suggestion. Automatic updates.<br>
| Here is my reason as to why I feel this is probably the most important<br>
| feature you need to implement.<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.6 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_blank">http://enigmail.mozdev.org</a><br>
<br>
iD8DBQFIMmazf1hPnk3Z0cQRAvCVAKCIB6B3m/UmQfg0liObSLElA0uBDgCg1fJe<br>
M6e6o7CzN1oxPBEEUM2cXak=<br>
=lkkw<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br>