[or-cvs] r12686: When the DANGEROUS_VERSION controller status event told us w (in tor/trunk: . doc/spec src/or)

[arma@xxxxxxxx]

Author: arma
Date: 2007-12-05 14:32:58 -0500 (Wed, 05 Dec 2007)
New Revision: 12686

Modified:
   tor/trunk/ChangeLog
   tor/trunk/doc/spec/control-spec.txt
   tor/trunk/src/or/networkstatus.c
Log:
When the DANGEROUS_VERSION controller status event told us we're
running an obsolete version, it used the string "OLD" to describe
it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
"OBSOLETE" in both cases.


Modified: tor/trunk/ChangeLog
===================================================================
--- tor/trunk/ChangeLog	2007-12-05 19:24:12 UTC (rev 12685)
+++ tor/trunk/ChangeLog	2007-12-05 19:32:58 UTC (rev 12686)
@@ -14,8 +14,8 @@
     - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
       requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
       crashing or mis-answering these requests.
-    - Stop being so aggressive about fetching dir info if your DirPort is
-      on but your ORPort is off.
+    - Stop being so aggressive about fetching v2 dir info if your
+      DirPort is on but your ORPort is off.
 
   o Minor bugfixes:
     - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
@@ -35,6 +35,10 @@
       clog everything up. Reported by Aljosha Judmayer.
     - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
       via autoconf.  Should fix compile on solaris.
+    - When the DANGEROUS_VERSION controller status event told us we're
+      running an obsolete version, it used the string "OLD" to describe
+      it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
+      "OBSOLETE" in both cases.
 
   o Minor features:
     - On USR1, when dmalloc is in use, log the top 10 memory

Modified: tor/trunk/doc/spec/control-spec.txt
===================================================================
--- tor/trunk/doc/spec/control-spec.txt	2007-12-05 19:24:12 UTC (rev 12685)
+++ tor/trunk/doc/spec/control-spec.txt	2007-12-05 19:32:58 UTC (rev 12686)
@@ -1162,15 +1162,16 @@
 
      DANGEROUS_VERSION
      "CURRENT=version"
-     "REASON=NEW/OLD/UNRECOMMENDED"
+     "REASON=NEW/OBSOLETE/UNRECOMMENDED"
      "RECOMMENDED=\"version, version, ...\""
        Tor has found that directory servers don't recommend its version of
        the Tor software.  RECOMMENDED is a comma-and-space-separated string
        of Tor versions that are recommended.  REASON is NEW if this version
-       of Tor is newer than any recommended version, OLD if this version of
-       Tor is older than any recommended version, and UNRECOMMENDED if
-       some recommended versions of Tor are newer and some are old than this
-       version.
+       of Tor is newer than any recommended version, OBSOLETE if
+       this version of Tor is older than any recommended version, and
+       UNRECOMMENDED if some recommended versions of Tor are newer and
+       some are older than this version. (The "OBSOLETE" reason was called
+       "OLD" from Tor 0.1.2.3-alpha up to and including 0.2.0.12-alpha.)
 
        {Controllers may want to suggest that the user upgrade OLD or
        UNRECOMMENDED versions.  NEW versions may be known-insecure, or may

Modified: tor/trunk/src/or/networkstatus.c
===================================================================
--- tor/trunk/src/or/networkstatus.c	2007-12-05 19:24:12 UTC (rev 12685)
+++ tor/trunk/src/or/networkstatus.c	2007-12-05 19:32:58 UTC (rev 12686)
@@ -1479,7 +1479,7 @@
       have_warned_about_old_version = 1;
       control_event_general_status(LOG_WARN, "DANGEROUS_VERSION "
            "CURRENT=%s REASON=%s RECOMMENDED=\"%s\"",
-           VERSION, status == VS_OLD ? "OLD" : "UNRECOMMENDED",
+           VERSION, status == VS_OLD ? "OBSOLETE" : "UNRECOMMENDED",
            recommended);
     }
   }