diff --git a/data/security.sgml b/data/security.sgml
index 5ad2430a5d..723a5b6b21 100644
--- a/data/security.sgml
+++ b/data/security.sgml
@@ -1,5 +1,5 @@
+
%includes;
]>
@@ -14,7 +14,7 @@
FreeBSD Security Guide
-Last Updated: $Date: 1997-02-15 06:45:27 $
+Last Updated: $Date: 1997-02-15 13:28:51 $
This guide attempts to document some of the tips and tricks used by
many FreeBSD security experts for securing systems and writing secure
@@ -41,10 +41,10 @@ to introduce security holes in the first place.
- Never trust any source of input, i.e. command line
arguments, environment variables, configuration files, incoming UDP packets,
- hostname lookups, etc. If the length or contents of the data received
- is at all subject to outside control then the program should watch
- for this when copying it around. Specific security issues to watch for
- in this area are:
+ hostname lookups, function arguments, etc. If the length or contents of
+ the data received is at all subject to outside control then the program
+ or function should watch for this when copying it around. Specific
+ security issues to watch for in this area are:
- strcpy() and sprintf() calls from
diff --git a/en/security.sgml b/en/security.sgml
index 5ad2430a5d..723a5b6b21 100644
--- a/en/security.sgml
+++ b/en/security.sgml
@@ -1,5 +1,5 @@
+
%includes;
]>
@@ -14,7 +14,7 @@
FreeBSD Security Guide
-Last Updated: $Date: 1997-02-15 06:45:27 $
+Last Updated: $Date: 1997-02-15 13:28:51 $
This guide attempts to document some of the tips and tricks used by
many FreeBSD security experts for securing systems and writing secure
@@ -41,10 +41,10 @@ to introduce security holes in the first place.
- Never trust any source of input, i.e. command line
arguments, environment variables, configuration files, incoming UDP packets,
- hostname lookups, etc. If the length or contents of the data received
- is at all subject to outside control then the program should watch
- for this when copying it around. Specific security issues to watch for
- in this area are:
+ hostname lookups, function arguments, etc. If the length or contents of
+ the data received is at all subject to outside control then the program
+ or function should watch for this when copying it around. Specific
+ security issues to watch for in this area are:
- strcpy() and sprintf() calls from