cvs commit: www manifesto.html

jeroen at jeroen at
Sun Mar 14 15:43:42 PST 2004

jeroen      04/03/14 16:43:42

  Modified:    .        manifesto.html
  Added:       hlfs     manifesto.html
  Add HLFS manifesto
  Revision  Changes    Path
  1.1                  www/hlfs/manifesto.html
  Index: manifesto.html
  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "">
  <html xmlns="" xml:lang="en">
  	<title>HLFS Manifesto - Linux From Scratch</title>
  	<meta name="description" content="Linux From Scratch - build your own Linux distribution from scratch" />
  	<meta name="keywords" content="Linux, LinuxFromScratch, Linux From Scratch, build your own Linux, DIY Linux, do-it-yourself Linux, create your own Linux" />
  	<meta name="MSSmartTagsPreventParsing" content="true" />
  	<link rel="alternate stylesheet" type="text/css" href="style/3columns.css" media="screen" title="ThreeColumn" />
  	<link rel="stylesheet" type="text/css" href="style/2columns.css" media="screen" title="TwoColumn" />
  	<link rel="alternate stylesheet" type="text/css" href="style/2columns-menu.css" media="screen" title="TwoColumnMenu" />
  	<link rel="stylesheet" type="text/css" href="style/print.css" media="print" />
  	<link rel="icon" href="images/favicon.ico" type="image/x-icon" />
  	<script type="text/javascript" src="scripts/styleswitcher.js"></script>
  <body class="root">
  <div id="header">
  	<ul id="sectionnav">
  		<li><a href="#content" class="hidden" accesskey="2">Skip to content</a></li>
  		<li><a href="lfs/news.html" accesskey="l"><span class="accesskey">L</span>FS</a></li>
  		<li><a href="blfs/news.html" accesskey="b"><span class="accesskey">B</span>eyond LFS</a></li>
  		<li><a href="alfs/news.html" accesskey="a"><span class="accesskey">A</span>utomated LFS</a></li>
  		<li><a href="hints/list.html" accesskey="h"><span class="accesskey">H</span>ints</a></li>
  		<li><a href="patches/news.html" accesskey="p"><span class="accesskey">P</span>atches</a></li>
  	<h1><a href="lfs/news.html" accesskey="l" title="LFS News page">Linux From Scratch</a></h1>
  	<div id="search">
  		<form method="get" action="">
  			<label title="Enter your search terms"><input size="20" type="text" name="query" onfocus="if(this.value==this.defaultValue) this.value='';" value="enter text here" maxlength="255" accesskey="s" /></label>
  			<label title="Submit the search terms"><input type="submit" value="search" /></label><br />
  			<a href="search.html" title="For more search options, click here" accesskey="4"><span class="accesskey">S</span>earch options</a>
  	<ul id="styleselect">
  		<li>Select layout:</li>
  		<li><a href="#" onclick="setActiveStyleSheet('TwoColumn'); return false;" title="Content (2 columns) | Navigation">Two columns</a></li>
  		<li><a href="#" onclick="setActiveStyleSheet('TwoColumnMenu'); return false;" title="Content (2 columns) | Navigation, general navigation as menu">Two columns, Menu</a></li>
  		<li><a href="#" onclick="setActiveStyleSheet('ThreeColumn'); return false;" title="Navigation|Content|Navigation">Three columns</a></li>
  <div id="container">
  <div id="content">
  	<em><a href="#generalnav" class="hidden">Skip to sitewide navigation</a></em>
  <h2>HLFS Mission Statement 2004-03-05 09:44:03 -0500</h2>
  <p>The HLFS team provides the "Hardened LFS" book, which teaches some foundational security principles and how to make an LFS/BLFS system more secure.</p>
  <p>The HLFS team addresses</p>
   <li>both LFS and BLFS installations, in varying degrees;</li>
   <li>various environments, configurations and applications;</li>
   <li>basic security policies and strategies;</li>
   <li>implementation of those policies and strategies.</li>
  <p>The HLFS team will produce a product that</p>
   <li>does not replace the (B)LFS books;</li>
   <li>does not provide basic education delivered in the (B)LFS books;</li>
   <li>does not supplant commonly available documents, resources or education;</li>
   <li>may apply to multiple platforms (with x86 being the focus).</li>
  <p>Produce a book that, in reasonable degree</p>
        <li>A) results in a user that is better educated in security issues;</li>
        <li>B) delivers a platform less vulnerable to local and network attacks;</li>
        <li>C) offers less vulnerability to exploits of OS component weaknesses;</li>
        <li>D) remains current as the environment changes;</li>
        <li>E) uses the (B)LFS books as a foundation.</li>
        <li>A) User education will be promoted by
           <li>1) providing an overview of common security concerns;</li>
           <li>2) presuming a user's security awareness to be minimal;</li>
           <li>3) offering a reasonably comprehensive, but concise, discussion of alternate security policy issues;</li>
           <li>4) limiting discussion to a level suited to users who have already successfully installed and are using a (B)LFS platform (i.e. "intermediate-to-advanced" users);</li>
           <li>5) publicly discussing any and all issues related to security and book content;</li>
           <li>6) implementing the strategies below.</li>
        <li>B) A platform less vulnerable to network attacks is addressed by
           <li>1) providing guidance to basic security policy that may be most appropriate to given environments, configurations and applications;</li>
           <li>2) demonstrating procedures, processes and commands that implement the selected policy on a platform produced via the (B)LFS books.</li>
        <li>C) Exploit-ability of OS components will be reduced by
           <li>1) discussing common weaknesses of OS components;</li>
           <li>2) presenting various types of solutions ("hardening");</li>
           <li>3) providing commands and supporting text that provide "hardening".</li>
        <li>D) To keep the book current, the team will
           <li>1) monitor certain security-related resources on the Internet and communicate and incorporate pertinent changes;</li>
           <li>2) monitor (B)LFS list activity for advance notice of changes;</li>
           <li>3) minimize maintenance effort from (B)LFS book activity by carefully selecting what to include directly and what to reference;</li>
           <li>4) "release" as close as reasonable to a new (B)LFS book release.</li>
        <li>E) To use the (B)LFS books as a foundation, the team will
           <li>1) incorporate certain parts of those books, when needed for clarity and/or educational benefit;</li>
           <li>2) avoid unneeded repetition of (B)LFS book contents;</li>
           <li>3) make liberal use of references to those books, and other pertinent resources, when such references are relevant to the topic at hand (but outside the scope of the book) and will enhance its value.</li>
  <p>Due to the enormity of the subject matter, workload associated with the effort and requirement for timeliness, success can only be ensured by distributing the tasks among the members of the HLFS community. For this reason, volunteers will be solicited to make a commitment to certain areas that will support the strategy detailed above. Note that one person may occupy multiple roles and multiple people may occupy one role. The important item is that the responsibilities are adequately addressed.</p>
  <p>Following are functions that need to be formally satisfied:</p>
  	<li>provide assistance to the team in conversion of text to the format needed to generate the book;</li>
  	<li>ensure style, wording, readability, presentation consistency, and completeness;</li>
  	<li>ensure overall communication with {B,H,}LFS occurs as appropriate;</li>
  	<li>ensure various security-related resources are effectively monitored for valuable input;</li>
  	<li>ensure we have topic experts with subject area responsibility, who generate and maintain text and commands that are specific to a certain topic within the scope of the book, stay aware of (B)LFS book and environmental changes that affect that area, and communicate appropriately with HLFS and (B)LFS team members;</li>
  	<li>pre-release verification - verify that processes detailed in the book provide the expected results and confirm that the resulting platform operates correctly.</li>
  <p>The HLFS book will not specify replacement of (B)LFS book-specified components unless there is no reasonable alternative to accomplish a needed goal.</p>
  <p>The team will not sacrifice completeness, robustness or accuracy for the sake of timeliness.</p>
  <p><a href="/manifesto.html">Back to the manifesto index</a></p>
  </div> <!-- end content -->
  <div id="generalnav">
  				<li><a href="donation.html" title="Donate via paypal">Make a donation</a></li>
  				<li><a href="" title="Get counted!">Register as LFS user</a></li>
  				<li><a href="becomemirror.html" title="If you have some bandwidth to spare">Become a mirror</a></li>
  				<li><a href="faq/" title="Frequently Asked Questions (and answers!)">FAQ</a></li>
  				<li><a href="search.html" title="Advanced search page">Search</a></li>
  				<li><a href="irc.html" title="Chat channels and nick names">IRC</a></li>
  				<li><a href="newsgroups.html" title="For following development and advanced support">News groups</a></li>
  				<li><a href="mail.html" title="For following development and advanced support">Mailing lists</a></li>
  				<li><a href="people.html" title="Who is who and who does what">The LFS team</a></li>
  				<li><a href="organization.html" title="Manifesto, Scope, Bounds, Objectives, Strategy and Logistics">General Documents</a></li>
  				<li><a href="manifesto.html" title="An index of all manifesto's">Team Mission Statements</a></li>
  				<li><a href="acknowledgements.html" title="People from past and present who contributed">Acknowledgements</a></li>
  				<li><a href="index.html" title="Home (mirror list)" accesskey="1">Home (Mirror list)</a></li>
  				<li><a href="sitemap.html" title="Structured overview of the website" accesskey="3">Sitemap</a></li>
  				<li><a href="accesskeys.html" title="Keyboard shortcuts for this site" accesskey="0">Accesskeys</a></li>
  				<li><a href="website.html" title="General info about this site" class="currentpage">Website information</a></li>
  				<li><a href="" title="Mail us if you run into problems with this website" accesskey="9">Contact webmaster</a></li>
  </div><!-- end generalnav -->
  </div><!-- end container -->
  <div id="footer">
  		<li><a href="#header">Back to the top.</a></li>
  		<li>© 1998-2003  Gerard Beekmans.</li>
  		<li>Website design by <a href="">Jeroen Coumans</a>.</li>
  		<li><a href=""><img src="images/xhtml-1.1.png" alt="Valid XHTML 1.1!" title="Validate this page's structure" height="15" width="80" /></a></li>
  		<li><a href=""><img src="images/css.png" alt="Valid CSS!" title="Validate this page's style" height="15" width="80" /></a></li>
  1.2       +1 -0      www/manifesto.html
  Index: manifesto.html
  RCS file: /home/cvsroot/www/manifesto.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- manifesto.html	14 Mar 2004 23:24:55 -0000	1.1
  +++ manifesto.html	14 Mar 2004 23:43:42 -0000	1.2
  @@ -56,6 +56,7 @@
   		<li><a href="bugzilla-manifesto.html">Bugzilla manifesto</a></li>
   		<li><a href="faq/manifesto.html">FAQ manifesto</a></li>
   		<li><a href="hints/manifesto.html">Hints manifesto</a></li>
  +		<li><a href="hlfs/manifesto.html">HLFS manifesto</a></li>
   		<li><a href="patches/manifesto.html">Patches manifesto</a></li>
   		<li><a href="website-manifesto.html">Website manifesto</a></li>

More information about the website mailing list