Stop logging identifying bridge info at 'notice'

A client running with bridges logs "new bridge descriptor '$NICKNAME'" and the bridge IP address at level 'notice'.

If the bridge has both an IPv4 and an IPv6 ORPort, there's an additional log line, this too at the 'notice' level.

There might be more.

changed milestone to %Tor: unspecified

added component::core tor/tor intro milestone::Tor: unspecified points::2 priority::medium resolution::duplicate scrubbing severity::normal sponsor::S-can status::closed tor-bridge type::defect labels

We could scrub the nickname and IP addresses (when SafeLogging 1).

Trac:
Reviewer: N/A to N/A
Milestone: N/A to Tor: 0.2.9.x-final

Trac:
Points: N/A to small/medium

Trac:
Keywords: N/A deleted, tor-bridge added
Sponsor: N/A to SponsorS-can

small/medium => 2.

Trac:
Points: small/medium to 2

Trac:
Keywords: N/A deleted, isaremoved added
Milestone: Tor: 0.2.9.x-final to Tor: 0.2.???

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:
Keywords: N/A deleted, tor-03-unspecified-201612 added
Milestone: Tor: 0.3.??? to Tor: unspecified

Remove an old triaging keyword.

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

Trac:
Keywords: isaremoved deleted, N/A added

Trac:
Keywords: tor-bridge deleted, tor-bridge intro scrubbing added

Looks like the same ticket as #17193 (moved) ?

#17193 (moved)

Trac:
Resolution: N/A to duplicate
Status: new to closed

closed

changed time estimate to 16h

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