diff --git a/en/security/advisories.xml b/en/security/advisories.xml
index 19e9516163..8b336aefac 100644
--- a/en/security/advisories.xml
+++ b/en/security/advisories.xml
@@ -1,10 +1,10 @@
-
+
%includes;
]>
-
+
&header;
@@ -66,19 +66,19 @@ HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/public_key.asc">PGP key
following releases of FreeBSD:
-- The most recent official release of FreeBSD.
-
- FreeBSD-current.
-
- FreeBSD-stable, when at least 2 releases are based on it.
+
- The most recent official release of FreeBSD.
+- FreeBSD-current.
+- FreeBSD-stable, when at least 2 releases are based on it.
- The previous FreeBSD-stable when a "new stable" does not yet
- have 2 releases based on it.
+ have 2 releases based on it.
At this time, security advisories are available for:
-- FreeBSD 3.3
-
- FreeBSD 3.4
-
- FreeBSD-current
-
- FreeBSD-stable
+
- FreeBSD 3.3
+- FreeBSD 3.4
+- FreeBSD-current
+- FreeBSD-stable
Older releases are not maintained and users are strongly encouraged
@@ -90,11 +90,11 @@ After a couple of days and some testing, the fix is retrofitted into
the supported FreeBSD-stable branch(es) and an advisory then sent
out.
-Advisories are sent to the following FreeBSD mailing lists:
+
Advisories are sent to the following FreeBSD mailing lists:
-- FreeBSD-security-notifications@FreeBSD.org
-
- FreeBSD-security@FreeBSD.org
-
- FreeBSD-announce@FreeBSD.org
+
- FreeBSD-security-notifications@FreeBSD.org
+- FreeBSD-security@FreeBSD.org
+- FreeBSD-announce@FreeBSD.org
@@ -175,7 +175,7 @@ and if you would like to unsubscribe from a mailing list:
Secure Programing Guidelines
-
+
- Never trust any source of input, i.e. command line arguments,
environment variables, configuration files, incoming TCP/UDP/ICMP packets,
hostname lookups, function arguments, etc. If the length of or contents of
@@ -341,13 +341,13 @@ walk on the stack.
- Always close file descriptors as soon as you can - this makes it more
likely that the stdio buffer contents will be discarded. In library
routines, always set any file descriptors that you open to close-on-exec.
-
+
FreeBSD Security Tips and Tricks
There are several steps one must take to secure a FreeBSD system, or
-in fact any Unix system:
+in fact any Unix system:
- Disabling potentially dangerous software
@@ -369,31 +369,31 @@ the time.
Not only remove programs that you don't use, also remove services you
don't want or need to provide. This can be done by editing the
/etc/inetd.conf and /etc/rc.conf files and turning
-off all services you don't use.
+off all services you don't use.
- Fixing software which has security bugs (or how to stay one step ahead
of crackers)
Make sure you are subscribed to various FreeBSD Security
mailing lists so you get updates on security bugs and
-fixes. Apply the fixes immediately.
+fixes. Apply the fixes immediately.
- Backups - repair your system if a security breach does occur
Always have backups and a clean version of the operating system (e.g. on
CD-Rom).
Make sure your backups do not contain corrupted data or
-data modified by attackers.
+data modified by attackers.
- Install software to watch the state of the system
Programs like the tcp wrappers and tripwire (both in packages/ports) can
help you to monitor activity on your system. This makes it easier
to detect break-ins. Also read outputs of the /etc/security scripts
-which are run daily and mailed to the root account.
+which are run daily and mailed to the root account.
- Educating the people who work on the system
Users should know what they are doing. They should be told to never give
out their password to anyone and to also use hard-to-guess passwords.
Let them understand that the security of the system/network is partly
-in their hands.
+in their hands.
diff --git a/en/security/security.sgml b/en/security/security.sgml
index 19e9516163..8b336aefac 100644
--- a/en/security/security.sgml
+++ b/en/security/security.sgml
@@ -1,10 +1,10 @@
-
+
%includes;
]>
-
+
&header;
@@ -66,19 +66,19 @@ HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/public_key.asc">PGP key
following releases of FreeBSD:
-- The most recent official release of FreeBSD.
-
- FreeBSD-current.
-
- FreeBSD-stable, when at least 2 releases are based on it.
+
- The most recent official release of FreeBSD.
+- FreeBSD-current.
+- FreeBSD-stable, when at least 2 releases are based on it.
- The previous FreeBSD-stable when a "new stable" does not yet
- have 2 releases based on it.
+ have 2 releases based on it.
At this time, security advisories are available for:
-- FreeBSD 3.3
-
- FreeBSD 3.4
-
- FreeBSD-current
-
- FreeBSD-stable
+
- FreeBSD 3.3
+- FreeBSD 3.4
+- FreeBSD-current
+- FreeBSD-stable
Older releases are not maintained and users are strongly encouraged
@@ -90,11 +90,11 @@ After a couple of days and some testing, the fix is retrofitted into
the supported FreeBSD-stable branch(es) and an advisory then sent
out.
-Advisories are sent to the following FreeBSD mailing lists:
+
Advisories are sent to the following FreeBSD mailing lists:
-- FreeBSD-security-notifications@FreeBSD.org
-
- FreeBSD-security@FreeBSD.org
-
- FreeBSD-announce@FreeBSD.org
+
- FreeBSD-security-notifications@FreeBSD.org
+- FreeBSD-security@FreeBSD.org
+- FreeBSD-announce@FreeBSD.org
@@ -175,7 +175,7 @@ and if you would like to unsubscribe from a mailing list:
Secure Programing Guidelines
-
+
- Never trust any source of input, i.e. command line arguments,
environment variables, configuration files, incoming TCP/UDP/ICMP packets,
hostname lookups, function arguments, etc. If the length of or contents of
@@ -341,13 +341,13 @@ walk on the stack.
- Always close file descriptors as soon as you can - this makes it more
likely that the stdio buffer contents will be discarded. In library
routines, always set any file descriptors that you open to close-on-exec.
-
+
FreeBSD Security Tips and Tricks
There are several steps one must take to secure a FreeBSD system, or
-in fact any Unix system:
+in fact any Unix system:
- Disabling potentially dangerous software
@@ -369,31 +369,31 @@ the time.
Not only remove programs that you don't use, also remove services you
don't want or need to provide. This can be done by editing the
/etc/inetd.conf and /etc/rc.conf files and turning
-off all services you don't use.
+off all services you don't use.
- Fixing software which has security bugs (or how to stay one step ahead
of crackers)
Make sure you are subscribed to various FreeBSD Security
mailing lists so you get updates on security bugs and
-fixes. Apply the fixes immediately.
+fixes. Apply the fixes immediately.
- Backups - repair your system if a security breach does occur
Always have backups and a clean version of the operating system (e.g. on
CD-Rom).
Make sure your backups do not contain corrupted data or
-data modified by attackers.
+data modified by attackers.
- Install software to watch the state of the system
Programs like the tcp wrappers and tripwire (both in packages/ports) can
help you to monitor activity on your system. This makes it easier
to detect break-ins. Also read outputs of the /etc/security scripts
-which are run daily and mailed to the root account.
+which are run daily and mailed to the root account.
- Educating the people who work on the system
Users should know what they are doing. They should be told to never give
out their password to anyone and to also use hard-to-guess passwords.
Let them understand that the security of the system/network is partly
-in their hands.
+in their hands.
diff --git a/share/sgml/advisories.xml b/share/sgml/advisories.xml
index 19e9516163..8b336aefac 100644
--- a/share/sgml/advisories.xml
+++ b/share/sgml/advisories.xml
@@ -1,10 +1,10 @@
-
+
%includes;
]>
-
+
&header;
@@ -66,19 +66,19 @@ HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/public_key.asc">PGP key
following releases of FreeBSD:
-- The most recent official release of FreeBSD.
-
- FreeBSD-current.
-
- FreeBSD-stable, when at least 2 releases are based on it.
+
- The most recent official release of FreeBSD.
+- FreeBSD-current.
+- FreeBSD-stable, when at least 2 releases are based on it.
- The previous FreeBSD-stable when a "new stable" does not yet
- have 2 releases based on it.
+ have 2 releases based on it.
At this time, security advisories are available for:
-- FreeBSD 3.3
-
- FreeBSD 3.4
-
- FreeBSD-current
-
- FreeBSD-stable
+
- FreeBSD 3.3
+- FreeBSD 3.4
+- FreeBSD-current
+- FreeBSD-stable
Older releases are not maintained and users are strongly encouraged
@@ -90,11 +90,11 @@ After a couple of days and some testing, the fix is retrofitted into
the supported FreeBSD-stable branch(es) and an advisory then sent
out.
-Advisories are sent to the following FreeBSD mailing lists:
+
Advisories are sent to the following FreeBSD mailing lists:
-- FreeBSD-security-notifications@FreeBSD.org
-
- FreeBSD-security@FreeBSD.org
-
- FreeBSD-announce@FreeBSD.org
+
- FreeBSD-security-notifications@FreeBSD.org
+- FreeBSD-security@FreeBSD.org
+- FreeBSD-announce@FreeBSD.org
@@ -175,7 +175,7 @@ and if you would like to unsubscribe from a mailing list:
Secure Programing Guidelines
-
+
- Never trust any source of input, i.e. command line arguments,
environment variables, configuration files, incoming TCP/UDP/ICMP packets,
hostname lookups, function arguments, etc. If the length of or contents of
@@ -341,13 +341,13 @@ walk on the stack.
- Always close file descriptors as soon as you can - this makes it more
likely that the stdio buffer contents will be discarded. In library
routines, always set any file descriptors that you open to close-on-exec.
-
+
FreeBSD Security Tips and Tricks
There are several steps one must take to secure a FreeBSD system, or
-in fact any Unix system:
+in fact any Unix system:
- Disabling potentially dangerous software
@@ -369,31 +369,31 @@ the time.
Not only remove programs that you don't use, also remove services you
don't want or need to provide. This can be done by editing the
/etc/inetd.conf and /etc/rc.conf files and turning
-off all services you don't use.
+off all services you don't use.
- Fixing software which has security bugs (or how to stay one step ahead
of crackers)
Make sure you are subscribed to various FreeBSD Security
mailing lists so you get updates on security bugs and
-fixes. Apply the fixes immediately.
+fixes. Apply the fixes immediately.
- Backups - repair your system if a security breach does occur
Always have backups and a clean version of the operating system (e.g. on
CD-Rom).
Make sure your backups do not contain corrupted data or
-data modified by attackers.
+data modified by attackers.
- Install software to watch the state of the system
Programs like the tcp wrappers and tripwire (both in packages/ports) can
help you to monitor activity on your system. This makes it easier
to detect break-ins. Also read outputs of the /etc/security scripts
-which are run daily and mailed to the root account.
+which are run daily and mailed to the root account.
- Educating the people who work on the system
Users should know what they are doing. They should be told to never give
out their password to anyone and to also use hard-to-guess passwords.
Let them understand that the security of the system/network is partly
-in their hands.
+in their hands.