Opened 20 months ago

Last modified 4 months ago

#18491 new defect

Stop logging identifying bridge info at 'notice'

Reported by: ln5 Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-bridge intro scrubbing
Cc: Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor: SponsorS-can

Description

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.

Child Tickets

Change History (11)

comment:1 Changed 20 months ago by ln5

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

comment:2 Changed 20 months ago by nickm

Milestone: Tor: 0.2.9.x-final

comment:3 Changed 19 months ago by nickm

Points: small/medium

comment:4 Changed 18 months ago by nickm

Keywords: tor-bridge added
Sponsor: SponsorS-can

comment:5 Changed 16 months ago by nickm

Points: small/medium2

small/medium => 2.

comment:6 Changed 14 months ago by isabela

Keywords: isaremoved added
Milestone: Tor: 0.2.9.x-finalTor: 0.2.???

comment:7 Changed 11 months ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:8 Changed 10 months ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

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

comment:9 Changed 5 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:10 Changed 5 months ago by nickm

Keywords: isaremoved removed

comment:11 Changed 4 months ago by nickm

Keywords: intro scrubbing added
Note: See TracTickets for help on using tickets.