Nickname registration message is confusing

toralf says:

wrt to this syslog massage : "You specified a server "zwiebeltoralf" by name, but the directory authorities do not have any key registered for this nickname"    - how can I register my nickname ?

We should change this message to be clearer, particularly because we don't use the Named/Unnamed flags any more.

We could just say "don't have any relay for this nickname".

changed milestone to %Tor: 0.3.2.x-final

added actualpoints::0.1 component::core tor/tor easy log-message milestone::Tor: 0.3.2.x-final owner::nickm parent::12898 points::0.2 priority::medium resolution::fixed severity::normal status::closed tor-client type::defect labels

Agreed.

(We did rip out the rest of the Named code, right?)

(And, are there other log messages that are from back when we had the Named flag?)

We ripped out a lot of the Named code; there is still a bunch around. I'd love to see somebody pick up the tickets for that

I actually think that the only thing that was missing was stem tests to raise coverage above what it was previoulsy or something, I don't recall anymore. I will eventually pick it up, but not soon.

Milestone renamed

Trac:
Milestone: Tor: 0.2.??? to Tor: 0.3.???

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Trac:
Milestone: Tor: 0.3.??? to Tor: unspecified
Keywords: N/A deleted, tor-03-unspecified-201612 added

Remove an old triaging keyword.

Trac:
Keywords: tor-03-unspecified-201612 deleted, N/A added

Trac:
Milestone: Tor: unspecified to Tor: 0.3.2.x-final
Owner: N/A to nickm
Keywords: N/A deleted, tor-client log-message added
Status: new to assigned

bug20488_029 has a fix here.

Trac:
Actualpoints: N/A to 0.1
Status: assigned to needs_review

Trac:
Parent: N/A to #12898 (moved)

Patch looks good to me!

(It changes one instance of 'server' to 'relay' but leaves the other one alone. But that's ok if you meant to do it.)

Trac:
Status: needs_review to merge_ready

Also a sentence in the changes file reads awkwardly. I suggest removing going.

IIUC "a going concern" is an idiom, but I guess it's not well-known enough.

Fixup commit pushed for both issues, including the third "server" :)

Squashed as bug20488_029_squashed, and merged to 0.3.2. Not backporting.

Trac:
Status: merge_ready to closed
Resolution: N/A to fixed

closed

changed time estimate to 1h 36m

added 48m of time spent

moved to tpo/core/tor#20488 (closed)