Feature #9579

Always display domain instead if IP in Tor Monitor

Added by alant 2015-06-15 09:17:28 . Updated 2015-09-10 16:16:32 .

Status:
Resolved
Priority:
Normal
Assignee:
alant
Category:
Tor configuration
Target version:
2016
Start date:
2015-06-15
Due date:
% Done:

100%

Feature Branch:
Type of work:
Test
Blueprint:

Starter:
Affected tool:
Tor Monitor
Deliverable for:

Description

TorMonitor should display DOMAIN:PORT information (like Vidalia does) instead of IP:PORT? See Feature #9298#note-5 for background info about it.

Files

domain-name.png (26170 B) sajolida, 2015-08-27 09:45:37

Subtasks

History

#1 Updated by alant 2015-06-15 09:21:13

  • Status changed from New to In Progress
  • Assignee changed from alant to intrigeri
  • QA Check set to Info Needed

alant wrote:
> TorMonitor should display DOMAIN:PORT information (like Vidalia does) instead of IP:PORT? See Feature #9298#note-5 for background info about it.

Have you seen a case where Vidalia shows the domain and TorMontitor does not? According to my tests, TorMonitor do show the domain when it’s privided by Tor, which is not always the case (I suspect NS resolution being sometimes sepatared from actual connection).

If you’ve seen cases where domain is displayed by Vidalia and not by TorMonitor, yould you please hint me how to reproduce them?

#2 Updated by alant 2015-06-15 09:24:58

  • Affected tool set to Tor Monitor

#3 Updated by intrigeri 2015-06-18 09:46:23

  • Assignee changed from intrigeri to alant

> Have you seen a case where Vidalia shows the domain and TorMontitor does not?

I don’t remember. Assume that I didn’t, then. Perhaps I was just confused by /code/attachments/download/664/tormonitor-main.png.

> According to my tests, TorMonitor do show the domain when it’s privided by Tor, which is not always the case

Cool :)

> (I suspect NS resolution being sometimes sepatared from actual connection).

Well, it depends on how the application works. If it handles DNS resolution separately, and then requests a TCP connection via Tor, then indeed Tor can’t correlate them. If it properly does SOCKS with DNS resolution delegated to Tor, then Tor has all the info it needs and then Tor Monitor should do the right thing => IMO, next step is to check, for the most important use case (that is, Tor Browser) that should do things correctly, that Tor Monitor indeed displays the correct destination hostname. It seems that the setup you already have allows you to easily answer this question, so: does it?

#4 Updated by alant 2015-06-24 15:12:34

> IMO, next step is to check, for the most important use case (that is, Tor Browser) that should do things correctly, that Tor Monitor indeed displays the correct destination hostname. It seems that the setup you already have allows you to easily answer this question, so: does it?

I don’t have this setup currently but can try next time I hack on Tor Monitor (this setup is Tails Jessie + TorMonitor manually installed).

#5 Updated by alant 2015-08-17 15:37:29

  • QA Check deleted (Info Needed)

> > IMO, next step is to check, for the most important use case (that is, Tor Browser) that should do things correctly, that Tor Monitor indeed displays the correct destination hostname. It seems that the setup you already have allows you to easily answer this question, so: does it?
>
> I don’t have this setup currently but can try next time I hack on Tor Monitor (this setup is Tails Jessie + TorMonitor manually installed).

I verified and unfortunately there are hostnames that are displaied in Vidalia and not in Tor Monitor.

Unfortunately I don’t know how to get better informations from stem.

#6 Updated by sajolida 2015-08-27 09:45:41

Actually, you’re doing that already :) See domain-name.png in attachment. The thing is the domain name is replaced by the IP almost immediately. Why does this happen?

#7 Updated by alant 2015-08-30 04:35:10

sajolida wrote:
> Actually, you’re doing that already :) See domain-name.png in attachment.

Great! Thanks for the findings!

> The thing is the domain name is replaced by the IP almost immediately. Why does this happen?

I don’t know why this happens, but it looks like stem first provide the hostname for the stream, and then replace it by the IP I currently update stream info when they are updated by stem, perhaps I shouldn’t.

#8 Updated by intrigeri 2015-08-30 05:28:10

> I currently update stream info when they are updated by stem, perhaps I shouldn’t.

If possible, updating all stream info except the hostname/IP would be nice.

Also, I wonder if displaying both the hostname and IP address would be useful, e.g. to correlate this with information coming from external sources that expose the IP address only. Granted, for most users this would just clutter the interface, so if there’s an easy way to make it opt-in or non invasive (tooltip? right panel?), great… otherwise forget it.

#9 Updated by sajolida 2015-09-07 10:52:19

  • Target version changed from Sustainability_M1 to 2016

#10 Updated by alant 2015-09-10 16:16:32

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100

intrigeri wrote:
> > I currently update stream info when they are updated by stem, perhaps I shouldn’t.
>
> If possible, updating all stream info except the hostname/IP would be nice.
>
Done in commit fafb475

> Also, I wonder if displaying both the hostname and IP address would be useful, e.g. to correlate this with information coming from external sources that expose the IP address only. Granted, for most users this would just clutter the interface, so if there’s an easy way to make it opt-in or non invasive (tooltip? right panel?), great… otherwise forget it.

There is no such thing like setting yet, so i forgot it…