os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Remove magic tunnel daemon idea -- we've had one student give it a pass,

Browse source 
and while an interesting project, there are probably better ways for
students to get involved (and things more likely to get into the base
tree).
This commit is contained in:
Robert Watson 2009-03-12 09:57:27 +00:00
parent 375e1e27ae
commit 8057fa7fe0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=33921
1 changed files with 1 additions and 44 deletions
Download patch file Download diff file Expand all files Collapse all files

45
en/projects/ideas/ideas.xml
View file

@ -15,7 +15,7 @@ Ideas//EN"
<ideas>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.96 2009/03/12 07:30:50 imp Exp $
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.97 2009/03/12 09:46:36 rwatson Exp $
</cvs:keyword>
</cvs:keywords>
@ -964,49 +964,6 @@ destDir parameter.</li>
</desc>
</idea>
<idea class="soc2007" id="magtundaemon">
<title>Magic tunnel daemon</title>
<desc>
<p><strong>Technical contact</strong>: <a
href="mailto:phk@FreeBSD.org">Poul-Henning Kamp</a>, <a
href="mailto:mharvan@inf.ethz.ch">Matus Harvan</a><br />
<strong>WIP</strong>: <a
href="http://wiki.freebsd.org/mtund">http://wiki.freebsd.org/mtund</a></p>
<p>IP can be tunnelled over IP, UDP, TCP, SSH, DNS, HTTP and many other
protocols, and this means that it is often possible to get a
connection out through a firewall, but each of these encapsulations
require prior setup of a specific program for each encapsulation, and
the user must experiment to decide which one to use at any one time.
The super tunnel daemon should implement pluggable encapsulations and
make it automatically select the most efficient encapsulation that
works at any one time. The user should not notice transitions from one
encapsulation to another, apart from maybe a small delay.</p>
<p>Wanted features (not sorted or prioritized):</p>
<ul>
<li>Autodetection of the environment (DHCP, DNS, routing, ...) in a
non-offensive way (no global portscans allowed; asking via DHCP,
zeroconf or similar technologies is ok) as far as possible.</li>
<li>Plugin architecture for easy addition of further encapsulations.</li>
<li>Failover from one encapsulation to another.</li>
<li>Distinct configuration files for encapsulations which need to be
configured (e.g. proxy, authentication, ...).</li>
<li>Possibility to disable installed encapsulations.</li>
<li>Print/log hints for protocols which require some configuration,
e.g. telling the user to use keys and perhaps the ssh-agent for ssh.</li>
<li>Configurable additional plugin directories (for plugins installed
via the ports collection).</li>
<li>Log how it is able to tunnel the traffic (this also makes it useful
for finding unwanted holes in the configuration of a firewall).</li>
</ul>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Good knowledge of C.</li>
<li>Good knowledge about networks.</li>
</ul>
</desc>
</idea>
<idea class="soc" id="tcpipreg">
<title>TCP/IP regression test suite</title>