[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

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

#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:  teor
     Type:  defect                               |         Status:
 Priority:  Medium                               |  assigned
Component:  Core Tor/Tor                         |      Milestone:  Tor:
 Severity:  Normal                               |  0.2.8.x-final
 Keywords:  fallback, must-fix-before-028-rc,    |        Version:  Tor:
  easy                                           |  0.2.8.1-alpha
Parent ID:                                       |     Resolution:
 Reviewer:                                       |  Actual Points:
                                                 |         Points:  small
                                                 |        Sponsor:
-------------------------------------------------+-------------------------
Changes (by teor):

 * status:  needs_information => assigned
 * owner:   => teor


Comment:

 Replying to [comment:2 teor]:
 > '''Log Message Fix'''
 >
 > I'm happy to make a fix to the log message in this ticket, and get it in
 0.2.8.
 >
 > Do you have a suggested "less scary" wording, arma?
 > I'd go with:
 >
 > "[notice] The relay at IP:ORPort has changed its key from A to B. Trying
 a different relay."
 >
 > These messages will only occur on bootstrap, so I think it's ok to leave
 them at notice.
 > But there may be a few if a few fallbacks change keys.
 > And tails users will get then on every boot. Should we reduce them to
 info?
 >
 > Note that this wording and the change of log level will apply even if
 the relay is a guard.
 > Is this what we want? Or should we change it only for the fallback case?
 > (We can do this, there are functions that tell us when we're
 bootstrapping.)
 > If so, I'd say "info" for fallbacks, and "warn" for guards/authorities.

 This is all we need to do to fix this now. I can do it.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18812#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs