[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #11345 [BridgeDB]: BridgeDB should have QR codes for bridge lines

#11345: BridgeDB should have QR codes for bridge lines
-------------------------+-------------------------------------------------
     Reporter:  isis     |      Owner:  isis
         Type:           |     Status:  closed
  enhancement            |  Milestone:
     Priority:  minor    |    Version:
    Component:           |   Keywords:  bridgedb-ui, bridgedb-https,
  BridgeDB               |  bridgedb-0.2.4, isis2014Q3Q4, bridgedb-0.3.0
   Resolution:  fixed    |  Parent ID:
Actual Points:           |
       Points:           |
-------------------------+-------------------------------------------------

Comment (by eighthave):

 I think the `bridge:` URI will work a lot better if it fits into the
 standard definitions of the bits of a "hierarchical URI", i.e.

 `scheme://user:password@host:port/path?key=value&another=true`

 Most systems provide parsers that make it trivial to get the pieces of
 URI, for example `android.net.Uri` or `java.net.URI`.  So maybe for
 bridges it would be something like:

 `bridge://user:password@xxxxxxxxxxxxxx:29461/scramblesuit?hash=a93fb6cf0709b8e732f300ff237f8cd51e5b6a7f`

 So `user` is user, `password` is password, `host` is the IP addres, `port`
 is the port, `path` is the bridge type, and everything else is in the
 query string as key/value pairs.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11345#comment:18>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs