- Remove the appletalk and securemines entries. [1]

- Add a new entry called "RFC3442 support". [2]

Discussed with: rwatson [1]
Submitted by:   emaste [2]
This commit is contained in:
Joel Dahl 2006-04-27 13:28:36 +00:00
parent 339785dc62
commit a42c1e28c2
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=27649

View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/projects/ideas/index.sgml,v 1.38 2006/04/22 12:00:04 joel Exp $">
<!ENTITY date "$FreeBSD: www/en/projects/ideas/index.sgml,v 1.39 2006/04/24 11:43:55 joel Exp $">
<!ENTITY title "FreeBSD list of projects and ideas for volunteers">
<!ENTITY % navincludes SYSTEM "../../includes.navdevelopers.sgml"> %navincludes;
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
@ -113,17 +113,14 @@
<li><a href="#p-iapp">IAPP preauthentication support in hostapd</a></li>
<li><a href="#p-wi">Bring wi(4) up to par with the current state of affairs
in the WLAN infrastructure</a></li>
<li><a href="#p-appletalk">Re-factor Apple Talk into a kernel module</a></li>
<li><a href="#p-flightmode">"Flight mode" for the loader</a></li>
</ul>
<h3>Security</h3>
<ul>
<li><a href="#p-securemines">SecureMines</a></li>
</ul>
<h3>Userland / Installation Tools</h3>
<ul>
<li><a href="#p-rfc3442">RFC3442 support</a></li>
<li><a href="#p-sysinstall">Small sysinstall renovation</a></li>
<li><a href="#p-sysinstall2">Extract the partition and slice table editor
from sysinstall</a></li>
@ -1008,29 +1005,6 @@
<hr>
<a name="p-appletalk"></a>
<h2>Re-factor Apple Talk into a kernel module</h2>
<p>At the moment the Apple Talk protocol is only available as a compile time
option. The goal of this item is to allow to load the Apple Talk protocol
at runtime (as part of netgraph or as a "standalone" module) and to add
appropriate locking (as a start even a generic subsystem lock would be ok,
more fine grained locking can be added later).</p>
<p><strong>Benefits</strong>:</p>
<ul>
<li>No need to rebuild the kernel.</li>
<li>No speed decrease of other network protocols when Apple Talk is used
(because of degrading the entire network stack into non-MPSAFE mode).</li>
</ul>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Knowledge of C.</li>
<li>Knowledge of Apple Talk.</li>
<li>Knowledge of the network stack.</li>
<li>Maybe knowledge of netgraph.</li>
</ul>
<hr>
<a name="p-flightmode"></a>
<h2>"Flight mode" for the loader</h2>
<p>Not every airline allows to use radio transmitters like WLAN-NIC's in
@ -1052,20 +1026,23 @@
<hr>
<a name="p-securemines"></a>
<h2>SecureMines</h2>
<a name="p-rfc3442"></a>
<h2>RFC3442 support</h2>
<p><strong>Technical contact</strong>: <a
href="mailto:alfred@FreeBSD.org">&a.alfred;</a></p>
<p>Add meta-data to the system in order to trap intruders and provide an audit
log. The goal of this project is to create several means of marking an event
as a foreign act (such as opening a trap file) which halts the system and
provides as much information as possible, possibilities include using
extended attributes to tag such "mines".</p>
href="mailto:emaste@FreeBSD.org">&a.emaste;</a></p>
<p><strong>URL's</strong>: <a
href="http://www.ietf.org/rfc/rfc3442.txt">RFC3442</a></p>
<p>Add support for RFC3442, the Classless Static Route option, to the DHCP
client. The original DHCP specification includes a route option but it
supports only class-based routes, which are not very useful today.
RFC3442 adds support for specifying the netmask width for each static
route. Note that the ISC dhcp server does not natively support RFC3442, but
custom options of arbitrary byte strings can be encoded in its configuration
file.</p>
<p><strong>Requirements</strong>:</p>
<ul>
<li>Good knowledge of C.</li>
<li>Good understanding of the Unix process model.</li>
<li>Good understanding of the FreeBSD kernel.</li>
<li>Routing knowledge.</li>
</ul>
<hr>
@ -1313,6 +1290,7 @@
<li><strong>Networking</strong>:
<a href="mailto:alfred@FreeBSD.org">&a.alfred;</a>,
<a href="mailto:brooks@FreeBSD.org">&a.brooks;</a>,
<a href="mailto:rwatson@FreeBSD.org">&a.rwatson;</a>,
<a href="mailto:sam@FreeBSD.org">&a.sam;</a>.</li>
<li><strong>Release Engineering / Integration</strong>:
<a href="mailto:re@FreeBSD.org">Release Engineering Team</a>.</li>