[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 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.
> 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?
This doesn't sound like a bad idea for now, but maybe we should look into
automating it for the future.
> From the docs I assume we can't have multiple ServerTransportPlugin
lines and "select" one for the configured bridge in torrc. Vidalia would
need to add or remove STP depending on what the user wants. Does that
sound right?
>
Indeed, for every STP line a new transport(s) is started. You can't have
multiple STPs but only some of them enabled at a given time.
> Opinions?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6412#comment:5>
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