Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #13671
Closed (moved) (moved)
Open
Issue created Nov 05, 2014 by Yawning Angel@yawning

Circuit display is broken if bridges are being used.

Note: This may be a good thing, I'm not sure about what the correct behavior should be here yet (As in, there's both a implementation problem, and a design problem here).

The "implementation" problem:

[11-05 09:46:55] Torbutton WARN: Error: 552 Unrecognized key "ns/id/$A09D536DD1752D542E1FBB3C9CE4449D51298239"

This won't work. desc/id/ is what you want.

The "design" problem: Please think Really Hard about if displaying the IP address of a user's Bridge (or Guard under normal use for that matter) is an ok thing to do. In the Bridge use case, I'm currently in the "If it does display the Bridge IP, I'm going to bother them till they hide it" camp, mainly because making it easy for the user to inadvertently spread the IP address of the bridge they are using is a bad thing.

I'm open to being convinced otherwise on this, and I'm not sure if "the user inadvertently makes the guard they are using public via a screenshot" is a privacy concern or not. This is "less" of an issue since that doesn't have the potential to ruin the Guard for other users, unlike Bridges.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking