r927 - trunk

archaic at linuxfromscratch.org archaic at linuxfromscratch.org
Mon Jan 17 09:37:25 PST 2005


Author: archaic
Date: 2005-01-17 10:37:24 -0700 (Mon, 17 Jan 2005)
New Revision: 927

Modified:
   trunk/ssp.txt
Log:
Updated ssp.txt

Modified: trunk/ssp.txt
===================================================================
--- trunk/ssp.txt	2005-01-17 04:44:09 UTC (rev 926)
+++ trunk/ssp.txt	2005-01-17 17:37:24 UTC (rev 927)
@@ -1,6 +1,6 @@
 AUTHOR:		Robert Connolly <robert at linuxfromscratch dot org> (ashes)
 
-DATE:		2005-01-16
+DATE:		2005-01-17
 
 LICENSE:	Public Domain
 
@@ -16,7 +16,7 @@
 from stack smashing attacks. This is the single largest class of attacks and
 many security oriented vendors have added it to their default compiler. The
 overhead lost to this type of guard is minimal. In practice if the entire
-system is built with SSP users shouldn't notice any difference in preformance.
+system is built with SSP users shouldn't notice any difference in performance.
 
 The official homepage for ProPolice Smashing Stack Srotector is at:
 http://www.trl.ibm.com/projects/security/ssp/
@@ -37,7 +37,7 @@
 PREREQUISITES: None
 The frandom kernel patch is now required for SSP. This provides the erandom
 device and sysctl interface. Using erandom stops a serious entropy depletion
-problem while still providing urandom quality random bytes. Idealy you should
+problem while still providing urandom quality random bytes. Ideally you should
 reboot an frandom kernel before installing SSP, but SSP will build without it.
 If the erandom sysctl interface is missing from the system (vanilla kernel)
 then /dev/urandom will be used; if /dev/urandom is missing (chroot) then
@@ -91,7 +91,7 @@
 so the kill function can be kept in a shared object. In the Glibc patch the
 erandom device is used to gather a small amount of random bits for the gaurd
 value. /dev/log will also need to be present in chroot for syslog to log stack
-overflows. It is reccomended intrusion detection systems monitor the system
+overflows. It is recommended intrusion detection systems monitor the system
 logs for these alerts.
 
 http://www.linuxfromscratch.org/patches/downloads/glibc/\
@@ -279,7 +279,7 @@
 for each runtime. The system syslog daemon should also log each of these.
 
 Should a program on your system ever have a stack overflow you should get
-similiar messages in your logs and perhaps in the console controling the
+similar messages in your logs and perhaps in the console controling the
 program.
 
 ACKNOWLEDGMENTS:
@@ -407,3 +407,5 @@
 * Added sed command for version.c.
 * Added fstack_protector patch to Glibc in chapter 6.
 * Add note for -O3 and Python.
+[2005-01-17]
+* Fixed misspellings.




More information about the hints mailing list