Opened 16 months ago

Last modified 6 months ago

#26176 new defect

Display .onion services with "mixed" content in circuit display properly

Reported by: gk Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-torbutton, tbb-circuit-display
Cc: arthuredelstein Actual Points:
Parent ID: Points:
Reviewer: Sponsor: Sponsor27-can

Description

Assume you have an .onion service (say: https://blockchainbdgpzk.onion/) that includes clear-text resources (e.g. an ad iframe like https://bci-ads.blockchain.info/bci-ads/iframe).

What should the circuit display show as the circuit for this site? Clearly, the requests for the .onion service (and respective resources) and the the requests semming from the iframe can't go over the same circuit. Thus, there is no way the circuit display can show only one circuit for loading all of the website (as it ideally would).

What is happening right now: the circuit display first shows the .onion circuit. But then when the clearnet requests are issued, the code we have just replaces the first three hops of the .onion circuit with the nodes used for the clearnet resources retaining the other three hops in the display which gives the impression everything is sent over an .onion circuit.

It seems to me this is suboptimal. Better would be not to update the circuit display with the information from the clearnet circuit. But there might be an even better solution we want to deploy

Child Tickets

Change History (3)

comment:1 Changed 16 months ago by tom

I definitely agree we should not update the circuit display.

comment:2 Changed 6 months ago by gk

Sponsor: Sponsor27

comment:3 Changed 6 months ago by gk

Sponsor: Sponsor27Sponsor27-can

Adjusting sponsor tag.

Note: See TracTickets for help on using tickets.