Re: SLFS book chapter proposals

On Fri, Dec 19, 2003 at 07:38:18PM -0600, DJ Lucas wrote:
> 
> I dont' know exactly how feasible it would be to show common examples of 
> code that lead to the vulnerabilities mentioned in that chapter, but 
> it'd be nice to see exactly what to look for in the code to find these 
> vulnerabilities, also what not to do when writing your own programs.

There are books out there for that. While learning is the goal, this
book should be considered a base. A place to start learning, with many
links and some nice nuggets of wisdom strewn about. What makes it unique
is how it applies to LFS. Examples of code are beyond that scope.
However, a simple piece of test code to determine whether or not you are
building protected code is good. Just like the simple code in LFS to
test whether or not gcc was built properly.

> I personally would like to see this for each type of exploit mentioned 
> in the fundamental knowledge chapter.  Someone had mentioned in another 
> thread that this might be a 'hacker's howto' of sorts.  This seems 
> dangerous, but at the same time, how can you fix a vulnerability if you 
> don't understand how the exploit works in the first place?

Going into specifics on how exploits works is redundant and will cause
much bloat to the book.

-- 
Archaic

It is proper to take alarm at the first experiment on our liberties. We
hold this prudent jealousy to be the first duty of citizens and one of
the noblest characteristics of the late Revolution. The freemen of
America did not wait till usurped power had strengthened itself by
exercise and entangled the question in precedents. They saw all the
consequences in the principle, and they avoided the consequences by
denying the principle. We revere this lesson too much ... to forget it

- James Madison.

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-security
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page