Clicking on circuit in Onion Circuits doesn't display details when using bridge
|Type of work:||Code||Affected tool:||Onion Circuits|
- When I'm connected to Tor
- And open Onions Circuits
- And click on a circuit
- Then no details are displayed in the left pane
#2 Updated by sajolida about 1 year ago
- Subject changed from Clicking on circuit in Onion Circuits doesn't display details to Clicking on circuit in Onion Circuits doesn't display details when using bridge
Actually, this seems to happen only when using bridges, and not when connecting directly to Tor.
#7 Updated by sajolida about 1 year ago
- Assignee changed from sajolida to alant
- QA Check changed from Ready for QA to Info Needed
Sorry for the delay but I'm not sure how to test this. I tried:
- git reset --hard 9043a5a
- sudo cp onioncircuits /usr/bin/onioncircuits
And then I still get nothing when clicking on a circuit but the following trace in the background:
** (onioncircuits:4004): WARNING **: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Traceback (most recent call last): File "/usr/bin/onioncircuits", line 574, in display_node status_entry = self.controller.get_network_status(fingerprint) File "/usr/lib/python3/dist-packages/stem/control.py", line 1529, in get_network_status raise exc File "/usr/lib/python3/dist-packages/stem/control.py", line 1521, in get_network_status desc_content = self.get_info(query, get_bytes = True) File "/usr/lib/python3/dist-packages/stem/control.py", line 961, in get_info raise exc File "/usr/lib/python3/dist-packages/stem/control.py", line 913, in get_info stem.response.convert('GETINFO', response) File "/usr/lib/python3/dist-packages/stem/response/__init__.py", line 128, in convert message._parse_message(**kwargs) File "/usr/lib/python3/dist-packages/stem/response/getinfo.py", line 38, in _parse_message raise stem.InvalidArguments('552', 'GETINFO request contained unrecognized keywords: %s\n' % ', '.join(unrecognized_keywords), unrecognized_keywords) stem.InvalidArguments: GETINFO request contained unrecognized keywords: ns/id/7B1749DAE33496CAF4C829447AC2657322461044 During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/onioncircuits", line 518, in cb_treeselection_changed self.show_circuit_details(circuit) File "/usr/bin/onioncircuits", line 535, in show_circuit_details self.display_node(fp, nick) File "/usr/bin/onioncircuits", line 575, in display_node except stem.DescriptorUnavailable: AttributeError: 'module' object has no attribute 'DescriptorUnavailable' localuser:onioncircuits being removed from access control list
- Status changed from Fix committed to In Progress
Tested again in 2.3 and this is not fixed.
Indeed, commit 9043a5a was not imported as a quilt patch into the package shipped in Tails 2.3 (and given your test results above, it's not 100% clear to me that this commit would fix the problem anyway).
- Assignee changed from alant to sajolida
- QA Check changed from Dev Needed to Ready for QA
I tried again and found that my fix didn't work with stem 1.2 (in Tails). I fixed this issue and tested inside Tails 2.3, and confirm the fix works. However, I'm forced to use a generic exception. Given stem 1.4 is in jessie-backports, I'd argue for upgrading stem in Tails, but that's not blocking anything.