[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #11574 [Flashproxy]: flashproxy-client needs to support SOCKS arguments primarily
#11574: flashproxy-client needs to support SOCKS arguments primarily
----------------------------+-----------------
Reporter: infinity0 | Owner: dcf
Type: defect | Status: new
Priority: normal | Milestone:
Component: Flashproxy | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
----------------------------+-----------------
Description changed by infinity0:
Old description:
> At the moment, flashproxy-client takes a bunch of command-line arguments,
> that determine how it registers and talks to the bridge.
>
> These should really be done in the SOCKS arguments, since the argument
> values may change per Bridge. These include:
>
> {{{
> --facilitator, --facilitator-pubkey
> --register, --register-*
> --transport.
> }}}
>
> I would argue that the CLI arguments be deprecated. I would favour
> complete removal, but AIUI it is required for compatibility with older
> versions of Tor.
New description:
At the moment, flashproxy-client takes a bunch of command-line arguments,
that determine how it registers and talks to the bridge.
These should really be done in the Bridge line (and passed in via SOCKS
arguments), since the argument values may change per Bridge. These
include:
{{{
--facilitator, --facilitator-pubkey
--register, --register-*
--transport.
}}}
I would argue that the CLI arguments be deprecated. I would favour
complete removal, but AIUI it is required for compatibility with older
versions of Tor.
This may require #10671.
--
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11574#comment:1>
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