s/I/we/ in Sam's fuzzing description. Add missing Requirements header.

Use bulleted lists in some further items.

Suggested by:	netchild
This commit is contained in:
Robert Watson 2008-03-18 18:02:08 +00:00
parent ab32b2ed80
commit 1b72055eff
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=31687

View file

@ -15,7 +15,7 @@ Ideas//EN"
<ideas> <ideas>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0"> <cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd"> <cvs:keyword name="freebsd">
$FreeBSD: www/en/projects/ideas/ideas.xml,v 1.54 2008/03/18 13:17:26 rwatson Exp $ $FreeBSD: www/en/projects/ideas/ideas.xml,v 1.55 2008/03/18 17:44:47 rwatson Exp $
</cvs:keyword> </cvs:keyword>
</cvs:keywords> </cvs:keywords>
@ -1112,11 +1112,12 @@ destDir parameter.</li>
href="mailto:sam@FreeBSD.org">Sam Leffler</a></p> href="mailto:sam@FreeBSD.org">Sam Leffler</a></p>
<p>Build a "packet fuzzer" tool that can be used to build test suites to <p>Build a "packet fuzzer" tool that can be used to build test suites to
improve reliability of the 802.11 code against garbage data. There are improve reliability of the 802.11 code against garbage data. There are
various tools out but I'm not aware of any good ones that work with 802.11 various tools out but we're not aware of any good ones that work with 802.11
and are generally available. The basic idea is to write a packet and are generally available. The basic idea is to write a packet
injector/playback tool that's driven by a scripting language. Then you injector/playback tool that's driven by a scripting language. Then you
need to build up a database of test cases. It's also possibly important need to build up a database of test cases. It's also possibly important
to do time-based playback.</p> to do time-based playback.</p>
<p><strong>Requirements</strong>:</p>
<ul> <ul>
<li>Good knowledge of C.</li> <li>Good knowledge of C.</li>
<li>Wireless networking fundamentals.</li> <li>Wireless networking fundamentals.</li>
@ -1549,14 +1550,16 @@ New tests must be created; existing tests must be completed and updated.
href="mailto:csjp@FreeBSD.org">Christian Peron</a></p> href="mailto:csjp@FreeBSD.org">Christian Peron</a></p>
<p>The TrustedBSD Audit implementation allows fine-grained monitoring <p>The TrustedBSD Audit implementation allows fine-grained monitoring
of processes in a FreeBSD install. This task extends the Audit of processes in a FreeBSD install. This task extends the Audit
implementation to have specific support for Jails: it teaches the implementation to have specific support for Jails:</p>
audit kernel code how to handle the security properties of jails, <ul>
implements independent audit configurations and a trail for each <li>teach the audit kernel code how to handle the security
jail (possibly in addition to a global jail), and tags audit properties of jails,</li>
records with BSM zone tags to indicate which jail they came from. <li>implements independent audit configurations and a trail for
It also includes writing a test suite to confirm that it all works each jail (possibly in addition to a global jail),</li>
properly.</p> <li>tags audit records with BSM zone tags to indicate which jail
they came from,</li>
<li>write a test suite to confirm that it all works properly.</li>
</ul>
<p><strong>Requirements</strong>:</p> <p><strong>Requirements</strong>:</p>
<ul> <ul>
<li>Strong C programming skills.</li> <li>Strong C programming skills.</li>