[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: Stable releases - old versions
- To: or-talk@xxxxxxxxxxxxx
- Subject: Re: Stable releases - old versions
- From: Erilenz <erilenz@xxxxxxxxx>
- Date: Fri, 31 Jul 2009 05:39:09 -0400
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Fri, 31 Jul 2009 05:39:56 -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:mime-version:content-type:content-disposition; bh=dL4+ImPdLnENJTvZ8rAtWXfe+KoL/1C/V0Y88MWCctg=; b=vNyQckbesMbumvAQBhThKAn/m90jY+y/CbmfIh7NURPFMcysUzs/9kc1mWmr7DBadG 4sNqgp52HXiMvZfstER5zeLbqkcZvivNdABAwLnnWoPsmU6b3MewAmVGBqpifNDpTtAw Ux2TZLbVrH2VQVg8i7Xc4v8Fmfjv5hxZQ4kis=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-disposition; b=lC8Qd+kMtJZ0EVv7EZs5JSjZfxjK8aZMFtVWunn2pClzYP0F1n6f/ZlkJTOQhpHQz7 S/wPgFgMCF6MPxpJxH+vl3IbHtW7auNXetaR3TTgKW7bQVHYUSyUU4csBMNQGMMI+RBq t1Fph0f5RjmgzEYvFQVtHMCPab9Wb7Kq0FC70=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
* on the Thu, Jul 30, 2009 at 11:51:39PM -0400, grarpamp wrote:
> Related to the blox* thread.
> When 0.2.0.3x was marked stable, I went through and
> mailed all the contacts running old versions. Some
> profusly thanked, some silently updated, some ignored.
> It would be handy if...
> Upon marking and releasing a new stable branch, include
> in the release notes what the minimum recommended versions
> are and why [security breach, crashing, performance, needing
> to break backward compat going forward, etc]... only
> the really major reasons, just a few quotable lines. Some people
> were like, why bother?
> Make the contact field more of an encouraged option to use.
> Maybe only a third of nodes had valid addresses.
I like this idea. Perhaps the various package maintainers could be
lobbied to update the installation scripts to request a valid
contact email address on installation/upgrade?
> Make Tor emit a logline hourly or at least daily when it notices
> that it is old. Much more likely to stick out like that. Perhaps
> graduate the verbosity/capitalization if it detects itself is not
> in the current stable branch or older.
As well as logging, perhaps Tor should make an effort to send an
email to the local root account when it detects it is "too old".
Obviously, that wont work in many instances, eg Windows Tor servers,
but it would be an additional contact route...