[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #9013 [BridgeDB]: BridgeDB should pass pluggable transport shared-secrets to clients
#9013: BridgeDB should pass pluggable transport shared-secrets to clients
--------------------------+-------------------------------
Reporter: asn | Owner: isis
Type: defect | Status: needs_information
Priority: major | Milestone:
Component: BridgeDB | Version:
Resolution: | Keywords: pt
Actual Points: | Parent ID:
Points: |
--------------------------+-------------------------------
Comment (by asn):
Replying to [comment:10 sysrqb]:
> Replying to [comment:9 asn]:
> > looking at the code again, the extrainfo line looks indeed like this:
> > {{{
> > transport obfs666 6.6.6.6:6666
argone=/usr/local/bin/obfsproxy,shared_secret=xyzzy
> > }}}
>
> I think that using the path to the binary in an example will confuse
some people. Is there a reason a PT should ever send a file path as an
argument?
>
Ah, ok, here is another example:
{{{
transport obfs666 6.6.6.6:6666 argone=valueone,shared_secret=xyzzy
}}}
atm I can't think of a reason that a PT would ever send a file path, but
it could as well happen in the future.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9013#comment:11>
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