[tor-bugs] #18050 [Tor]: Relay submitted a descriptor with 0 DirPort due to a self-test race condition

[Tor Bug Tracker & Wiki]

#18050: Relay submitted a descriptor with 0 DirPort due to a self-test race
condition
-------------------------------------------------+-------------------------
 Reporter:  teor                                 |          Owner:
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:  Tor:
Component:  Tor                                  |  0.2.8.x-final
 Severity:  Normal                               |        Version:  Tor:
 Keywords:  026-maybe-backport, 027-maybe-       |  0.2.6.10
  backport                                       |     Resolution:
Parent ID:                                       |  Actual Points:
  Sponsor:                                       |         Points:
-------------------------------------------------+-------------------------

Comment (by starlight):

 Just remembered noticing earlier a strange last address-change date/time
 for my relay.  On looking I see it was affected by this glitch six months
 ago:

 last_changed_address_or_port:2015-06-12 18:00:00

 Have log entries for it:

 {{{
 06-12-17-cons:r Binnacle <fp> aWzbTbPNq8OoPHFtMnxMTVOHDuY 15:11:13
 108.53.208.157 443 80
 06-12-18-cons:r Binnacle <fp> dIaQvTy5UjVYtdRVa2xPDSwhpAw 17:49:21
 108.53.208.157 443 0
 06-12-19-cons:r Binnacle <fp> RoqngB0ium+unPem09nCwnzBqI4 18:32:44
 108.53.208.157 443 80
 }}}

 {{{
 Jun 12 18:49:17 Tor: Parsing GEOIP IPv4 file ./geoip.
 Jun 12 18:49:17 Tor: Configured to measure statistics. Look for the
 *-stats files that will first be written to the data directory in 24 hours
 from now.
 Jun 12 18:49:17 Tor: Your Tor server's identity key fingerprint is
 'Binnacle 4F0DB7E687FC7C0AE55C8F243DA8B0EB27FBF1F2'
 Jun 12 18:49:21 Tor: We now have enough directory information to build
 circuits.
 Jun 12 18:49:21 Tor: Bootstrapped 80%: Connecting to the Tor network.
 Jun 12 18:49:21 Tor: Self-testing indicates your ORPort is reachable from
 the outside. Excellent. Publishing server descriptor.
 Jun 12 18:49:22 Tor: Bootstrapped 85%: Finishing handshake with first hop.
 Jun 12 18:49:22 Tor: Bootstrapped 90%: Establishing a Tor circuit.
 Jun 12 18:49:23 Tor: Tor has successfully opened a circuit. Looks like
 client functionality is working.
 Jun 12 18:49:23 Tor: Bootstrapped 100%: Done.
 Jun 12 18:50:24 Tor: Self-testing indicates your DirPort is reachable from
 the outside. Excellent.
 Jun 12 18:51:25 Tor: Performing bandwidth self-test...done.
 }}}

 In this case DirPort=0 was published just before minute 50 and and
 DirPort=80 just after, but in the case of `kitten` both appear to have
 been pushed just before minute 50:

 {{{
 12-13-09-cons:r kitten1 <fp> vG0ZWLi31UXoqz4H2H/hweSvxqo 04:44:19
 62.210.124.124 9001 9030
 12-13-10-cons:r kitten1 <fp> vG0ZWLi31UXoqz4H2H/hweSvxqo 04:44:19
 62.210.124.124 9001 9030
 12-13-11-cons:r kitten1 <fp> yUnPgGOwhq5QfUEe1Eg0zKCU+w0 10:48:46
 62.210.124.124 9001 0
 12-13-12-cons:r kitten1 <fp> JrZF6+VnnYZuQHRllufg53dbjH8 10:49:48
 62.210.124.124 9001 9030
 12-13-13-cons:r kitten1 <fp> JrZF6+VnnYZuQHRllufg53dbjH8 10:49:48
 62.210.124.124 9001 9030
 }}}

 However I suspect the system clock on that relay's server is skewed and so
 the actual descriptor pushes were before and after the consensus vote
 event.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18050#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online