[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #6412 [Vidalia]: Add way to configure obfsproxy bridges
#6412: Add way to configure obfsproxy bridges
-----------------------+----------------------------------------------------
Reporter: Sebastian | Owner: chiiph
Type: defect | Status: new
Priority: normal | Milestone:
Component: Vidalia | Version:
Keywords: | Parent: #6434
Points: | Actualpoints:
-----------------------+----------------------------------------------------
Comment(by chiiph):
Replying to [comment:5 asn]:
> Replying to [comment:4 chiiph]:
> > My comment in here will be similar to what I said in #6435. The
simplest way for the user would be to have a transport combobox with all
the transports, and have the user select one of those or "None" and then
have everything else (in terms of GUI) be exactly the same.
> >
>
> Hm, the checkbox approach makes sense. Although remember that a bridge
can support multiple transports.
Ok, then I guess a list with checkboxes for each transport would be the
way to go.
>
> > Vidalia could have a configuration value in vidalia.conf to know what
transport are available.
> >
>
> Hm, I'm not sure how vidalia.conf works. It seems that this
configuration value would have to change every time a transport/proxy was
added/removed. Are there any other vidalia.conf configuration values that
require human editing in new releases? Who is doing this editing atm?
Erinn?
>
In general, the conf doens't change, but if so, yes, Erinn handles the
changes (or may be Shondoit).
> This doesn't sound like a bad idea for now, but maybe we should look
into automating it for the future.
>
How would we automate something like this? The scenario we need to define
is one where the user understand only that there is a thing called
"transport" (or whatever word is best) and that it does some magic when
bridges don't work for certain people.
So say we provide obfs2 for now. We can add the following to vidalia.conf:
Transport="Obfs2:<STP line>"
So Vidalia knows Obfs2 exists and it should use the corresponding STP line
when the configured bridge is using this transport.
If in the future we distribute another transport, we need to tell Vidalia
about it:
Transport="Obfs2:<STP line>; Blabla:<Other STP line>"
And so on.
But somehow Vidalia needs to know what transport there are, otherwise we
need to ask the user to set that, in which case the user needs to know
what to write. The advanced user can have a plugin that modifies that
specific line in the configuration in a nice GUI way.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6412#comment:6>
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