Re: SLFS book chapter proposals

Robert Day <[email protected]>
Newsgroups gmane.linux.lfs.security
Message-ID <[email protected]>
On Sun, 2003-12-21 at 20:14, Christos Gioran wrote:

> 
> The point not clarified (at least IMO) as of yet is whether we will mention 
> only differences from the LFS book or list *all* compilation commands. My 
> proposal is that after deciding on the contents of the book, we will have a 
> clear idea of the extent of differences. If it is tolerable then document the 
> differences only. Otherwise (most probably) we will have to include all 
> instructions from the beginning.
> 
The only problem I have with patching the LFS book so to speak, is that
there may be some more in-depth issues with local application
hardening...  ie. the base GCC builds insecure applications, so we
replace that with a secure gcc that builds hardened apps...  How many
applications have to bre rebuilt? Will that break anything? What about
libraries? Do we have to rebuild glibc in a hardened mode? How many
applications and packages will that break, and have to rebuild against
the new glibc?  It may very well become far bigger a project than a
fresh build...
And again, if publication is the end goal here, it has to be a contained
book, with most everything included in the book, at bare minimum,
everything needed to build the SLFS system - so it could be SLFS and LFS
published in the same book I guess, but is that really the best way?

  Rob Day (BOFH)


-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-security
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.