- tor-commits - lists.torproject.org

[torspec/master] Add a reminder to control-spec that server descs aren't default now
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit f811e9eb07e672c1d58f86f7c3470574c3b53715 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 10:39:07 2012 -0500 Add a reminder to control-spec that server descs aren't default now Clients now download microdescriptors, not full server descriptors, by default. desc/* was tripping people up. --- control-spec.txt | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/control-spec.txt b/control-spec.txt index 5792cef..5d12322 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -471,7 +471,10 @@ *append* to the ExitPolicy config option. "desc/id/<OR identity>" or "desc/name/<OR nickname>" -- the latest - server descriptor for a given OR. + server descriptor for a given OR. (Note that modern Tor clients + do not download server descriptors by default, but download + microdescriptors instead. If microdescriptors are enabled, you'll + need to use md/* instead.) "md/id/<OR identity>" or "md/name/<OR nickname>" -- the latest microdescriptor for a given OR. [First implemented in @@ -508,7 +511,7 @@ queries. [First implemented in 0.2.0.13-alpha.] "desc/all-recent" -- the latest server descriptor for every router that - Tor knows about. + Tor knows about. (See note about desc/id/* and desc/name/* above.) "network-status" -- a space-separated list (v1 directory style) of all known OR identities. This is in the same format as the

1 0

[torspec/master] Oops; use the right limit for extra-info docs
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit b66c9cec43f24e9bdb02cc8a83fe6ceebe7dbbe0 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 10:34:41 2012 -0500 Oops; use the right limit for extra-info docs --- dir-spec.txt | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index cb3fe46..8e389c9 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -354,8 +354,9 @@ http://<hostname:port>/tor/ - Neither router descriptors nor extra-info documents may exceed 20,000 - bytes in length. If they do, the authorities SHOULD reject them. + Router descriptors may not exceed 20,000 bytes in length; extra-info + documents may not exceed 50,000 bytes in length. If they do, the + authorities SHOULD reject them. 2.1. Router descriptor format

1 0

[torspec/master] Document MEASUREMENT_EXPIRED
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit de621605527e0f48c8ef07c492e4c58d8701fd21 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 10:36:24 2012 -0500 Document MEASUREMENT_EXPIRED --- control-spec.txt | 5 ++++- 1 files changed, 4 insertions(+), 1 deletions(-) diff --git a/control-spec.txt b/control-spec.txt index 1a50256..5792cef 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -1354,7 +1354,10 @@ if extended events are enabled (see 3.19). Clients MUST accept reasons not listed above. Reasons are as given in tor-spec.txt, except for: - NOPATH (Not enough nodes to make circuit) + NOPATH (Not enough nodes to make circuit) + MEASUREMENT_EXPIRED (As "TIMEOUT", except that we had left the circuit + open for measurement purposes to see how long it + would take to finish.) The "REMOTE_REASON" field is provided only when we receive a DESTROY or TRUNCATE cell, and only if extended events are enabled. It contains the

1 0

[torspec/master] Make proposals 117, 208 (ipv6 exits) as finished.
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit 3d0d39292cb10146a74aecddde9a3cc2bffc2177 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 10:30:53 2012 -0500 Make proposals 117, 208 (ipv6 exits) as finished. ("Finished" means we still need to merge them into tor-spec. Additionally, I've removed the parts of tor-spec that say "we don't do IPv6" as no longer true.) --- proposals/000-index.txt | 8 ++++---- proposals/117-ipv6-exits.txt | 3 ++- proposals/208-ipv6-exits-redux.txt | 4 ++-- tor-spec.txt | 7 ------- 4 files changed, 8 insertions(+), 14 deletions(-) diff --git a/proposals/000-index.txt b/proposals/000-index.txt index caec770..4a641a2 100644 --- a/proposals/000-index.txt +++ b/proposals/000-index.txt @@ -37,7 +37,7 @@ Proposals by number: 114 Distributed Storage for Tor Hidden Service Descriptors [CLOSED] 115 Two Hop Paths [DEAD] 116 Two hop paths from entry guards [DEAD] -117 IPv6 exits [ACCEPTED] +117 IPv6 exits [FINISHED] 118 Advertising multiple ORPorts at once [SUPERSEDED] 119 New PROTOCOLINFO command for controllers [CLOSED] 120 Shutdown descriptors when Tor servers stop [DEAD] @@ -128,7 +128,7 @@ Proposals by number: 205 Remove global client-side DNS caching [OPEN] 206 Preconfigured directory sources for bootstrapping [OPEN] 207 Directory guards [OPEN] -208 IPv6 Exits Redux [OPEN] +208 IPv6 Exits Redux [FINISHED] 209 Tuning the Parameters for the Path Bias Defense [OPEN] 210 Faster Headless Consensus Bootstrapping [OPEN] 211 Internal Mapaddress for Tor Configuration Testing [OPEN] @@ -180,7 +180,6 @@ Proposals by status: 205 Remove global client-side DNS caching 206 Preconfigured directory sources for bootstrapping [for 0.2.4.x] 207 Directory guards [for 0.2.4.x] - 208 IPv6 Exits Redux [for 0.2.4.x] 209 Tuning the Parameters for the Path Bias Defense [for 0.2.4.x+] 210 Faster Headless Consensus Bootstrapping [for 0.2.4.x+] 211 Internal Mapaddress for Tor Configuration Testing [for 0.2.4.x+] @@ -189,7 +188,6 @@ Proposals by status: 214 Allow 4-byte circuit IDs in a new link protocol 215 Let the minimum consensus method change with time ACCEPTED: - 117 IPv6 exits [for 0.2.4.x] 140 Provide diffs between consensuses 147 Eliminate the need for v2 directories in generating v3 directories [for 0.2.4.x] 157 Make certificate downloads specific [for 0.2.4.x] @@ -203,6 +201,7 @@ Proposals by status: 098 Proposals that should be written 099 Miscellaneous proposals FINISHED: + 117 IPv6 exits [for 0.2.4.x] [in 0.2.4.7-alpha] 121 Hidden Service Authentication [in 0.2.1.x] 151 Improving Tor Path Selection 155 Four Improvements of Hidden Service Performance [in 0.2.1.x] @@ -211,6 +210,7 @@ Proposals by status: 161 Computing Bandwidth Adjustments [for 0.2.1.x] 162 Publish the consensus in multiple flavors [in 0.2.3.1-alpha] 180 Pluggable transports for circumvention [in 0.2.3.x] + 208 IPv6 Exits Redux [for 0.2.4.x] [in 0.2.4.7-alpha] CLOSED: 101 Voting on the Tor Directory System [in 0.2.0.x] 102 Dropping "opt" from the directory format [in 0.2.0.x] diff --git a/proposals/117-ipv6-exits.txt b/proposals/117-ipv6-exits.txt index 60ae332..9c51cf2 100644 --- a/proposals/117-ipv6-exits.txt +++ b/proposals/117-ipv6-exits.txt @@ -2,8 +2,9 @@ Filename: 117-ipv6-exits.txt Title: IPv6 exits Author: coderman Created: 10-Jul-2007 -Status: Accepted +Status: Finished Target: 0.2.4.x +Implemented-In: 0.2.4.7-alpha Overview diff --git a/proposals/208-ipv6-exits-redux.txt b/proposals/208-ipv6-exits-redux.txt index 6f83f3c..e25a901 100644 --- a/proposals/208-ipv6-exits-redux.txt +++ b/proposals/208-ipv6-exits-redux.txt @@ -2,9 +2,9 @@ Filename: 208-ipv6-exits-redux.txt Title: IPv6 Exits Redux Author: Nick Mathewson Created: 10-Oct-2012 -Status: Open +Status: Finished Target: 0.2.4.x - +Implemented-In: 0.2.4.7-alpha 1. Obligatory Motivation Section diff --git a/tor-spec.txt b/tor-spec.txt index a3df860..1099e3d 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -1060,7 +1060,6 @@ see tor-design.pdf. An address type (6) [1 octet] The IPv6 address to which the connection was made [16 octets] A number of seconds (TTL) for which the address may be cached [4 octets] - [XXXX No version of Tor currently generates the IPv6 format.] [Tor exit nodes before 0.1.2.0 set the TTL field to a fixed value. Later versions set the TTL to the last value seen from a DNS server, and expire @@ -1286,10 +1285,4 @@ see tor-design.pdf. cells when both a) the window is <= 450, and b) there are less than ten cell payloads remaining to be flushed at that edge. -A.1. Differences between spec and implementation - -- The current specification requires all ORs to have IPv4 addresses, but - allows relays to exit and resolve to IPv6 addresses, and to declare IPv6 - addresses in their exit policies. The current codebase has no IPv6 - support at all.

1 0

[torspec/master] Add some missing GETINFO info/names options
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit a14d7f33d4062aa20bc416603b7ef03916f928a0 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 10:28:13 2012 -0500 Add some missing GETINFO info/names options Fixes the items listed in 3844. --- control-spec.txt | 13 +++++++++++++ 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/control-spec.txt b/control-spec.txt index 6819905..1a50256 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -637,6 +637,9 @@ OptionName SP Documentation CRLF OptionPrefix SP Documentation CRLF OptionPrefix = OptionName "/*" + The OptionPrefix form indicates a number of options beginning with the + prefix. So if "config/*" is listed, other options beginning with + "config/" will work, but "config/*" itself is not an option. "events/names" A space-separated list of all the events supported by this version of @@ -708,6 +711,9 @@ "status/version/current" Status of the current version. One of: new, old, unrecommended, recommended, new in series, obsolete, unknown. + "status/version/num-concurring" + "status/version/num-versioning" + These options are deprecated; they no longer give useful information. "status/clients-seen" A summary of which countries we've seen clients from recently, formatted the same as the CLIENTS_SEEN status event described in @@ -724,6 +730,13 @@ A space-separated list of the addresses at which Tor is listening for connections of each specified type. [New in Tor 0.2.2.26-beta.] + "dir-usage" + A newline-separated list of how many bytes we've served to answer + each type of directory request. The format of each line is: + Keyword 1*SP Integer 1*SP Integer + where the first integer is the number of bytes written, and the second + is the number of requests answered. + Examples: C: GETINFO version desc/name/moria1 S: 250+desc/name/moria=

1 0

[torspec/master] Spec the maximum descriptor size.
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit b783355e8cf087ba427f4cc0db6e652540e9e272 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 10:18:41 2012 -0500 Spec the maximum descriptor size. Fixed 3176 --- dir-spec.txt | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/dir-spec.txt b/dir-spec.txt index e223b2a..cb3fe46 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -354,6 +354,9 @@ http://<hostname:port>/tor/ + Neither router descriptors nor extra-info documents may exceed 20,000 + bytes in length. If they do, the authorities SHOULD reject them. + 2.1. Router descriptor format Router descriptors consist of the following items. For backward

1 0

[torspec/master] SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA is not on the v1 ciphers list
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit 490c777859b96223421e247675367c792a031c75 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 10:14:49 2012 -0500 SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA is not on the v1 ciphers list Fixes #6963; reported by cced. --- tor-spec.txt | 6 ++---- 1 files changed, 2 insertions(+), 4 deletions(-) diff --git a/tor-spec.txt b/tor-spec.txt index 186b7c0..a3df860 100644 --- a/tor-spec.txt +++ b/tor-spec.txt @@ -181,7 +181,6 @@ see tor-design.pdf. TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA - SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA In "renegotiation" (a.k.a. "the v2 handshake"), the connection initiator sends no certificates, and @@ -335,9 +334,8 @@ see tor-design.pdf. If the client sends the Fixed Ciphersuite List, the responder MUST NOT select any ciphersuite besides TLS_DHE_RSA_WITH_AES_256_CBC_SHA, - TLS_DHE_RSA_WITH_AES_128_CBC_SHA, SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA, and - SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA: such ciphers might not actually be - supported by the client. + TLS_DHE_RSA_WITH_AES_128_CBC_SHA, and SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA: + such ciphers might not actually be supported by the client. If the client sends a v2+ ClientHello with a list of ciphers other then the Fixed Ciphersuite List, the responder can trust that the client

1 0

[tor/master] In comments and logs, say "UTC" not "GMT"
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit 864e15cd1c596b2a9dbc610d3aa78b49a4f33355 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 10:05:16 2012 -0500 In comments and logs, say "UTC" not "GMT" Fix for #6113. Note that the RFC1123 times we generate still all say 'GMT'. I'm going to suggest this is not worth changing. --- changes/bug6113 | 3 +++ src/common/tortls.c | 2 +- src/common/util.c | 11 ++++++----- src/or/confparse.h | 2 +- src/or/hibernate.c | 4 ++-- src/or/networkstatus.c | 4 ++-- src/or/statefile.c | 2 +- 7 files changed, 16 insertions(+), 12 deletions(-) diff --git a/changes/bug6113 b/changes/bug6113 new file mode 100644 index 0000000..436243d --- /dev/null +++ b/changes/bug6113 @@ -0,0 +1,3 @@ + o Trivial bugfixes: + - Fix log messages and comments to avoid saying "GMT" when we mean + "UTC". Fixes bug 6113. diff --git a/src/common/tortls.c b/src/common/tortls.c index 76924b3..af3059a 100644 --- a/src/common/tortls.c +++ b/src/common/tortls.c @@ -2077,7 +2077,7 @@ log_cert_lifetime(int severity, const X509 *cert, const char *problem) BIO_get_mem_ptr(bio, &buf); s2 = tor_strndup(buf->data, buf->length); - strftime(mytime, 32, "%b %d %H:%M:%S %Y GMT", tor_gmtime_r(&now, &tm)); + strftime(mytime, 32, "%b %d %H:%M:%S %Y UTC", tor_gmtime_r(&now, &tm)); log(severity, LD_GENERAL, "(certificate lifetime runs from %s through %s. Your time is %s.)", diff --git a/src/common/util.c b/src/common/util.c index 1b0603a..44cdd64 100644 --- a/src/common/util.c +++ b/src/common/util.c @@ -1342,7 +1342,7 @@ n_leapdays(int y1, int y2) static const int days_per_month[] = { 31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31}; -/** Compute a time_t given a struct tm. The result is given in GMT, and +/** Compute a time_t given a struct tm. The result is given in UTC, and * does not account for leap seconds. Return 0 on success, -1 on failure. */ int @@ -1383,10 +1383,11 @@ static const char *MONTH_NAMES[] = { "Jan", "Feb", "Mar", "Apr", "May", "Jun", "Jul", "Aug", "Sep", "Oct", "Nov", "Dec" }; -/** Set buf to the RFC1123 encoding of the GMT value of t. +/** Set buf to the RFC1123 encoding of the UTC value of t. * The buffer must be at least RFC1123_TIME_LEN+1 bytes long. * - * (RFC1123 format is Fri, 29 Sep 2006 15:54:20 GMT) + * (RFC1123 format is "Fri, 29 Sep 2006 15:54:20 GMT". Note the "GMT" + * rather than "UTC".) */ void format_rfc1123_time(char *buf, time_t t) @@ -1404,8 +1405,8 @@ format_rfc1123_time(char *buf, time_t t) memcpy(buf+8, MONTH_NAMES[tm.tm_mon], 3); } -/** Parse the RFC1123 encoding of some time (in GMT) from buf, - * and store the result in *t. +/** Parse the (a subset of) the RFC1123 encoding of some time (in UTC) from + * buf, and store the result in *t. * * Return 0 on success, -1 on failure. */ diff --git a/src/or/confparse.h b/src/or/confparse.h index f33208e..20616be 100644 --- a/src/or/confparse.h +++ b/src/or/confparse.h @@ -23,7 +23,7 @@ typedef enum config_type_t { CONFIG_TYPE_BOOL, /**< A boolean value, expressed as 0 or 1. */ CONFIG_TYPE_AUTOBOOL, /**< A boolean+auto value, expressed 0 for false, * 1 for true, and -1 for auto */ - CONFIG_TYPE_ISOTIME, /**< An ISO-formatted time relative to GMT. */ + CONFIG_TYPE_ISOTIME, /**< An ISO-formatted time relative to UTC. */ CONFIG_TYPE_CSV, /**< A list of strings, separated by commas and * optional whitespace. */ CONFIG_TYPE_LINELIST, /**< Uninterpreted config lines */ diff --git a/src/or/hibernate.c b/src/or/hibernate.c index 9e54eb4..7208996 100644 --- a/src/or/hibernate.c +++ b/src/or/hibernate.c @@ -890,12 +890,12 @@ hibernate_end_time_elapsed(time_t now) /* We weren't sleeping before; we should sleep now. */ log_notice(LD_ACCT, "Accounting period ended. Commencing hibernation until " - "%s GMT", buf); + "%s UTC", buf); hibernate_go_dormant(now); } else { log_notice(LD_ACCT, "Accounting period ended. This period, we will hibernate" - " until %s GMT",buf); + " until %s UTC",buf); } } } diff --git a/src/or/networkstatus.c b/src/or/networkstatus.c index f33de4c..63426e8 100644 --- a/src/or/networkstatus.c +++ b/src/or/networkstatus.c @@ -775,7 +775,7 @@ router_set_networkstatus_v2(const char *s, time_t arrived_at, long delta = now - ns->published_on; format_time_interval(dbuf, sizeof(dbuf), delta); log_warn(LD_GENERAL, "Network status from %s was published %s in the " - "future (%s GMT). Check your time and date settings! " + "future (%s UTC). Check your time and date settings! " "Not caching.", source_desc, dbuf, published); control_event_general_status(LOG_WARN, @@ -1874,7 +1874,7 @@ networkstatus_set_current_consensus(const char *consensus, format_iso_time(tbuf, c->valid_after); format_time_interval(dbuf, sizeof(dbuf), delta); log_warn(LD_GENERAL, "Our clock is %s behind the time published in the " - "consensus network status document (%s GMT). Tor needs an " + "consensus network status document (%s UTC). Tor needs an " "accurate clock to work correctly. Please check your time and " "date settings!", dbuf, tbuf); control_event_general_status(LOG_WARN, diff --git a/src/or/statefile.c b/src/or/statefile.c index beb9cf8..55ba0c1 100644 --- a/src/or/statefile.c +++ b/src/or/statefile.c @@ -416,7 +416,7 @@ or_state_save(time_t now) format_local_iso_time(tbuf, now); tor_asprintf(&contents, "# Tor state file last generated on %s local time\n" - "# Other times below are in GMT\n" + "# Other times below are in UTC\n" "# You *do not* need to edit this file.\n\n%s", tbuf, state); tor_free(state);

1 0

[tor/master] Note limitation of parse_rfc_1123_time
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit 99669c69b3ad424c02393c97b48795eba6fb36bb Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 10:06:16 2012 -0500 Note limitation of parse_rfc_1123_time RFC1123 suggests that we should handle two-year times, and a full range of time zones, and other stuff too. We don't. --- src/common/util.c | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/src/common/util.c b/src/common/util.c index 44cdd64..61d09aa 100644 --- a/src/common/util.c +++ b/src/common/util.c @@ -1408,6 +1408,9 @@ format_rfc1123_time(char *buf, time_t t) /** Parse the (a subset of) the RFC1123 encoding of some time (in UTC) from * buf, and store the result in *t. * + * Note that we only accept the subset generated by format_rfc1123_time above, + * not the full range of formats suggested by RFC 1123. + * * Return 0 on success, -1 on failure. */ int

1 0

[torspec/master] We mean UTC, not GMT. Fix bug 6113.
by nickm＠torproject.org 23 Nov '12

23 Nov '12

commit d581e631e7b89d354789d07c0513b6aef8977a72 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Nov 23 09:57:09 2012 -0500 We mean UTC, not GMT. Fix bug 6113. --- control-spec.txt | 16 ++++++++-------- dir-spec.txt | 12 ++++++------ 2 files changed, 14 insertions(+), 14 deletions(-) diff --git a/control-spec.txt b/control-spec.txt index 8a239d0..6819905 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -530,7 +530,7 @@ via the control interface; the 'all' target returns the mappings set through any mechanism. Expiry is formatted as with ADDRMAP events, except that "expiry" is - always a time in GMT or the string "NEVER"; see section 4.1.7. + always a time in UTC or the string "NEVER"; see section 4.1.7. First introduced in 0.2.0.3-alpha. "addr-mappings/*" -- as for address-mappings/*, but without the @@ -611,7 +611,7 @@ start and the rest of the interval respectively. The 'interval-start' and 'interval-end' fields are the borders of the current interval; the 'interval-wake' field is the time within the current interval (if any) - where we plan[ned] to start being active. The times are GMT. + where we plan[ned] to start being active. The times are UTC. "config/names" A series of lines listing the available configuration options. Each is @@ -1484,19 +1484,19 @@ Syntax: "650" SP "ADDRMAP" SP Address SP NewAddress SP Expiry - [SP Error] SP GMTExpiry CRLF + [SP Error] SP UTCExpiry CRLF NewAddress = Address / "<error>" Expiry = DQUOTE ISOTime DQUOTE / "NEVER" Error = "error=" ErrorCode ErrorCode = XXXX - GMTExpiry = "EXPIRES=" DQUOTE IsoTime DQUOTE + UTCExpiry = "EXPIRES=" DQUOTE IsoTime DQUOTE - Error and GMTExpiry are only provided if extended events are enabled. + Error and UTCExpiry are only provided if extended events are enabled. - Expiry is expressed as the local time (rather than GMT). This is a bug, - left in for backward compatibility; new code should look at GMTExpiry + Expiry is expressed as the local time (rather than UTC). This is a bug, + left in for backward compatibility; new code should look at UTCExpiry instead. These events are generated when a new address mapping is entered in the @@ -1991,7 +1991,7 @@ main relays, we might start sending these events in other cases too. TimeStarted is a quoted string indicating when the reported summary - counts from (in GMT). + counts from (in UTCS). The CountrySummary keyword has as its argument a comma-separated, possibly empty set of "countrycode=count" pairs. For example (without diff --git a/dir-spec.txt b/dir-spec.txt index 39edc0f..e223b2a 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -405,7 +405,7 @@ [Exactly once] - The time, in GMT, when this descriptor (and its corresponding + The time, in UTC, when this descriptor (and its corresponding extra-info document if any) was generated. "fingerprint" fingerprint NL @@ -606,7 +606,7 @@ [Exactly once.] - The time, in GMT, when this document (and its corresponding router + The time, in UTC, when this document (and its corresponding router descriptor if any) was generated. It MUST match the published time in the corresponding router descriptor. @@ -1010,14 +1010,14 @@ [Exactly once.] - The time (in GMT) when this document and corresponding key were + The time (in UTC) when this document and corresponding key were last generated. "dir-key-expires" YYYY-MM-DD HH:MM:SS NL [Exactly once.] - A time (in GMT) after which this key is no longer valid. + A time (in UTC) after which this key is no longer valid. "dir-signing-key" NL a key in PEM format @@ -1373,7 +1373,7 @@ signed (that is, not including the signature), encoded in base64. "Publication" is the publication time of its most recent descriptor, in the form - YYYY-MM-DD HH:MM:SS, in GMT. "IP" is its current IP address; + YYYY-MM-DD HH:MM:SS, in UTC. "IP" is its current IP address; ORPort is its current OR port, "DirPort" is its current directory port, or "0" for "none". @@ -2213,7 +2213,7 @@ Authorities MUST take pains to ensure that their clocks remain accurate within a few seconds. (Running NTP is usually sufficient.) - The first voting period of each day begins at 00:00 (midnight) GMT. If + The first voting period of each day begins at 00:00 (midnight) UTC. If the last period of the day would be truncated by one-half or more, it is merged with the second-to-last period.

1 0