[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #3203 [Pluggable transport]: obfsproxy will probably need a GUI on Windows
#3203: obfsproxy will probably need a GUI on Windows
---------------------------------+------------------------------------------
Reporter: asn | Owner: asn
Type: defect | Status: new
Priority: normal | Milestone:
Component: Pluggable transport | Version:
Keywords: | Parent:
Points: | Actualpoints:
---------------------------------+------------------------------------------
So, looking at my GSoC proposal I see:
{{{
c) Play with TBB to allow it to launch external proxies, so that
non-technical Windows users can use external proxies.
}}}
that was quite easy to type, but now that I actually think of it it starts
to seem quite painful.
The problem is that we will probably need a GUI that allows some minimal
configuration and outputs the status to the Windows user.
I brought this issue up on IRC some weeks ago and rransom said that we
will indeed probably need a GUI hack.
Thing is I don't know anything about 'Windows' or 'GUIs'. I don't even
know the absolute basics behind GUI coding.
This trac ticket is for ideas and advices on the interface of obfsproxy on
the Windows platform.
Is there a super-quick and "correct" way of doing that?
Don't forget that the "launch obfsproxy through TBB" operation is part of
the 'quick-n-dirty' plan, so that we can ship obfsproxy to a few bridge
users that can beta test it.
It's not the final release and it's not a clean way of using obfsproxy on
Windows. Maybe the GUI doesn't have to be uber-clean either.
[cc:ing rransom and nickm.
nick if you want me to stop ccing you, do say.]
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3203>
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