Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #6550

Closed (moved)
(moved)
Open
Created Aug 05, 2012 by Damian Johnson@atagar

Clarifications for extrainfo desc transport lines

Couple clarifications from discussions with asn...

  1. The 'transportname' in descriptor lines are unique

As discussed on ticket #6257 (closed), George is fine with the 'transportname' being unique per a descriptor. This is useful to me because I can now model this as a 'transportname => attributes' hash which will be more user friendly.

  1. The transport name can appear on non-bridges

Though this attribute only makes sense for bridges, it can appear on the extrainfo descriptors for non-bridges as well. Actually, we already have one in the wild...

extra-info toorvoid 0B37323298FF98CD86ED404895BB27B7426E8AE1 published 2012-08-04 12:19:13 transport obfs2 83.212.96.201:33570

Will upload a patch in a sec...

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