Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #19650

Closed (moved)
Open
Opened Jul 08, 2016 by cypherpunks@cypherpunks

Keep non-printable characters out of details documents

Future Tor will not publish non-ASCII descriptors and dir auths will reject them at some point.

Since this is quite far in the future, what do you think about removing such strings in onionoo (before it reaches tor)? I'm not suggesting to ignore the entire descriptor in such a case but just replace such chars with "?" ? "??B?" -> "??B??"

https://atlas.torproject.org/#details/21E84B294794821E2898E8ED18402E45E4FC351E

Note: I used "non-printable" (vs. non-ASCII) since onionoo data includes printable but non-ASCII chars.

https://lists.torproject.org/pipermail/tor-relays/2016-July/009667.html

related: [1] https://trac.torproject.org/projects/tor/ticket/19647 [2] https://trac.torproject.org/projects/tor/ticket/18938

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#19650