[tor-bugs] #3664 [Torouter]: Tor web interface for the DreamPlug

Tor Bug Tracker & Wiki torproject-admin at torproject.org
Fri Jul 29 20:25:15 UTC 2011


#3664: Tor web interface for the DreamPlug
----------------------+-----------------------------------------------------
 Reporter:  runa      |          Owner:  hellais
     Type:  task      |         Status:  new    
 Priority:  normal    |      Milestone:         
Component:  Torouter  |        Version:         
 Keywords:            |         Parent:         
   Points:            |   Actualpoints:         
----------------------+-----------------------------------------------------

Comment(by ioerror):

 Replying to [comment:1 hellais]:
 > I would like to know what the exact requirements for this web interface
 should be. What I deduce would be necessary is:
 >

 Sure thing, comments in line.

 > main page:
 >   The main page contains an overview of the current status of the Tor
 router. Status if it is connected properly to Tor or not, and general
 information on the current status of the network. If it is the first time
 that the user connects to the Torouter then it loads the wizard.

 That sounds like a reasonable flow.

 >
 > wizard:
 >   Guides the user through the steps of configuring the Torouter. @runa,
 @jake you would need to tell me exactly what the steps required should be.
 An example would be
 >    step 1: The user is asked how he will connect to the internet. He
 chooses DHCP or static or whatever.
 >    step 2: The user is asked how to configure his wifi network. ESSID,
 channel, etc.
 >    step 3: He is asked how to configure Tor.
 >   .. and so on. As I said I am not sure how you envisioned this. What
 are your ideas?
 >

 That sounds like a good start. We need at minimum, a way to set the eth0
 interface up, set the eth1 interface as a NAT network or not, run a wifi
 ap0, etc.

 > status:
 >   A detailed status page, containing more info than the main page.
 [insert specs for "detailed information" here]

 That sounds good too.

 >
 > config:
 >   The advanced configuration interface. A good value for
 customizability/not_breakability should be found. By this I mean what kind
 of users are Torouter users? A good compromise between what they can do
 and what they can't do to avoid breaking stuff should be found [insert
 specs for what should be customizable]
 >

 I think that we should have a very small web config for tor at this point
 - arm has the code for verifying config options, we should reuse it.

 > Is there anything else?

 Authentication, I suspect. :)

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/3664#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list