Damian Johnson commited on 2016-02-14 03:03:28
Zeige 1 geänderte Dateien mit 0 Einfügungen und 49 Löschungen.
Cristobal Leiva did this last year, so no longer relevant... https://leivaburto.github.io/sop-proposal/
| ... | ... |
@@ -595,7 +595,6 @@ meetings around the world.</li> |
| 595 | 595 |
<p> |
| 596 | 596 |
<b>Project Ideas:</b><br /> |
| 597 | 597 |
<i><a href="#txtorcon-stemIntegration">Txtorcon/Stem Integration</a></i><br /> |
| 598 |
- <i><a href="#relayWebPanel">Relay Web Status Panel</a></i><br /> |
|
| 599 | 598 |
</p> |
| 600 | 599 |
|
| 601 | 600 |
<a id="project-txtorcon"></a> |
| ... | ... |
@@ -896,54 +895,6 @@ meetings around the world.</li> |
| 896 | 895 |
bonus points if it's Twisted.</p> |
| 897 | 896 |
</li> |
| 898 | 897 |
|
| 899 |
- <a id="relayWebPanel"></a> |
|
| 900 |
- <li> |
|
| 901 |
- <b>Relay Web Status Dashboard</b> |
|
| 902 |
- <br> |
|
| 903 |
- Effort Level: <i>Medium</i> |
|
| 904 |
- <br> |
|
| 905 |
- Skill Level: <i>Medium</i> |
|
| 906 |
- <br> |
|
| 907 |
- Likely Mentors: <i>Damian (atagar)</i> |
|
| 908 |
- <p> |
|
| 909 |
- Relay operators presently have a good option for monitoring the status |
|
| 910 |
- of their relay: |
|
| 911 |
- <a href="https://www.atagar.com/arm/">arm</a> which uses |
|
| 912 |
- curses. This project would be to make a new kind of monitor specifically |
|
| 913 |
- for relay operators that provides a status dashboard site on localhost. |
|
| 914 |
- </p> |
|
| 915 |
- <p> |
|
| 916 |
- The interface will likely <a |
|
| 917 |
- href="https://www.atagar.com/arm/screenshots.php">borrow heavily from |
|
| 918 |
- arm</a>, except of course in areas where we can improve upon it. Two |
|
| 919 |
- important design constraints is that a localhost controller provides a |
|
| 920 |
- bigger attack surface than guis or curses, so we should be a little more |
|
| 921 |
- wary of what it does. This should be a read-only controller (ie, you can't |
|
| 922 |
- *do* anything to the relay) and by default not surface any sensitive |
|
| 923 |
- information (such as arm's connection panel). Also take a peek at <a |
|
| 924 |
- href="http://www.ntop.org/products/ntop/">ntop</a> for ideas on what we can |
|
| 925 |
- do with a web interface. |
|
| 926 |
- </p> |
|
| 927 |
- <p> |
|
| 928 |
- This project will likely include two parts: an AJAX site and a localhost |
|
| 929 |
- daemon to fulfill those requests. <a |
|
| 930 |
- href="https://stem.torproject.org/">Stem</a> is the backend of arm, and can |
|
| 931 |
- be used to get everything you see in arm's interface (making it a natural |
|
| 932 |
- choice for the daemon). That said, this project might entail some Stem |
|
| 933 |
- improvements if we run across any gaps. |
|
| 934 |
- </p> |
|
| 935 |
- <p> |
|
| 936 |
- Applicants should be familiar with Python, JavaScript, and learn about |
|
| 937 |
- <a href="https://stem.torproject.org/">Stem</a>. <b>As part of your |
|
| 938 |
- application for this project please make both mockups of the interface and |
|
| 939 |
- a proof of concept demo application using JS to surface something with |
|
| 940 |
- Stem. <a |
|
| 941 |
- href="https://trac.torproject.org/projects/tor/wiki/doc/stem/bugs">Involvement |
|
| 942 |
- with Stem development</a> during the application process is also a big |
|
| 943 |
- plus.</b> |
|
| 944 |
- </p> |
|
| 945 |
- </li> |
|
| 946 |
- |
|
| 947 | 898 |
<a id="torCleanup"></a> |
| 948 | 899 |
<li> |
| 949 | 900 |
<b>Tor Codebase Cleanup</b> |
| 950 | 901 |