Opened 6 years ago

Last modified 2 years ago

#8749 new enhancement

Return information about the leaking application

Reported by: bastik Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-client usability logging intro
Cc: Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor:

Description

Log from where the leaking request came.

When Tor says (in the Vidalia log):

Potentially Dangerous Connection! - One of your applications established a connection through Tor to "IP:PORT" using a protocol that may leak information about your destination. Please ensure you configure your applications to use only SOCKS4a or SOCKS5 with remote hostname resolution.

could Tor tell what port the connection was made from? Maybe the log could include SOCKS details (like username). I don't think it isn't able to identify the application.

Sure it's bad to use random stuff with Tor, but this information makes it easier to sort out applications that leak.

Child Tickets

Change History (6)

comment:1 Changed 6 years ago by nickm

Keywords: tor-client added
Milestone: Tor: 0.2.5.x-final

comment:2 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:3 Changed 3 years ago by teor

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

Milestone renamed

comment:4 Changed 3 years 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:5 Changed 2 years ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:6 Changed 2 years ago by nickm

Keywords: usability logging intro added
Points: 3
Severity: Normal
Note: See TracTickets for help on using tickets.