[tor-bugs] #18812 [Tor]: [warn] Tried connecting to router at 81.7.17.171:443, but identity key was not as expected: wanted 00C4B4731658D3B4987132A3F77100CFCB190D97 but got CFECDDCA990E3EF7B7EC958B22441386B6B8D820.

Wed Apr 13 07:23:05 UTC 2016

#18812: [warn] Tried connecting to router at 81.7.17.171:443, but identity key was
not as expected: wanted 00C4B4731658D3B4987132A3F77100CFCB190D97 but got
CFECDDCA990E3EF7B7EC958B22441386B6B8D820.
------------------------+--------------------------------
     Reporter:  arma    |      Owner:
         Type:  defect  |     Status:  new
     Priority:  Medium  |  Milestone:  Tor: 0.2.8.x-final
    Component:  Tor     |    Version:
     Severity:  Normal  |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |   Reviewer:
      Sponsor:          |
------------------------+--------------------------------
 I'm running git master, but I think this applies to Tor 0.2.8.2-alpha. On
 bootstrap, I got
 {{{
 [...]
 Apr 13 03:17:50.542 [notice] I learned some more directory information,
 but not enough to build a circuit: We have no usable consensus.
 Apr 13 03:17:50.620 [warn] Tried connecting to router at 81.7.17.171:443,
 but identity key was not as expected: wanted
 00C4B4731658D3B4987132A3F77100CFCB190D97 but got
 CFECDDCA990E3EF7B7EC958B22441386B6B8D820.
 Apr 13 03:17:52.147 [notice] Bootstrapped 40%: Loading authority key certs
 [...]
 }}}

 So I think everything is going according to plan (cool, I even used a
 fallback dir!), except my fallback dir seems to have changed its key since
 it went into fallback_dirs.inc.

 Maybe it isn't so reliably stable after all? :) :/

 I wonder if we should consider a) doing periodic full checks of the
 fallback relays, to catch issues like this one preemptively, and then b)
 making the warning less scary for normal users.

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