From 35c9348ef73098e57f46ab94a18839823bba42b4 Mon Sep 17 00:00:00 2001 From: Bill Fumerola Date: Mon, 31 May 1999 01:30:40 +0000 Subject: [PATCH] Add FreeBSD 3.{1,2} and remove FreeBSD 3.0 and FreeBSD 2.2.7 out of the supported security advisory page. Also, make a grammar change and a sgml nit while I'm here. --- en/security/advisories.xml | 12 ++++++------ en/security/security.sgml | 12 ++++++------ share/sgml/advisories.xml | 12 ++++++------ 3 files changed, 18 insertions(+), 18 deletions(-) diff --git a/en/security/advisories.xml b/en/security/advisories.xml index 702d861f17..28b3a74cbf 100644 --- a/en/security/advisories.xml +++ b/en/security/advisories.xml @@ -1,10 +1,10 @@ - + %includes; ]> - + &header; @@ -75,9 +75,9 @@ following releases of FreeBSD:

At this time, security advisories are available for: @@ -222,7 +222,7 @@ condition and that the permissions are correct.
  • If an attacker can force packets to go/come from another arbitrary system then that attacker has complete control over the data that we get -and NONEof it should be trusted. +and NONE of it should be trusted.

  • Never trust a configuration file is correctly formatted or that it was @@ -262,7 +262,7 @@ suid/sgid program.
  • If you are unsure of your security fixes, send them to a reviewer with whom you have already arrangements for a second glance over your code. Don't commit code you are not sure about since breaking something -in the name of security fix is rather embarrassing. +in the name of a security fix is rather embarrassing.

  • Those without CVS commit privileges should make sure that a reviewer diff --git a/en/security/security.sgml b/en/security/security.sgml index 66467f80e8..06eb423a27 100644 --- a/en/security/security.sgml +++ b/en/security/security.sgml @@ -1,10 +1,10 @@ - + %includes; ]> - + &header; @@ -75,9 +75,9 @@ following releases of FreeBSD:

    At this time, security advisories are available for: @@ -222,7 +222,7 @@ condition and that the permissions are correct.
  • If an attacker can force packets to go/come from another arbitrary system then that attacker has complete control over the data that we get -and NONEof it should be trusted. +and NONE of it should be trusted.

  • Never trust a configuration file is correctly formatted or that it was @@ -262,7 +262,7 @@ suid/sgid program.
  • If you are unsure of your security fixes, send them to a reviewer with whom you have already arrangements for a second glance over your code. Don't commit code you are not sure about since breaking something -in the name of security fix is rather embarrassing. +in the name of a security fix is rather embarrassing.

  • Those without CVS commit privileges should make sure that a reviewer diff --git a/share/sgml/advisories.xml b/share/sgml/advisories.xml index 702d861f17..28b3a74cbf 100644 --- a/share/sgml/advisories.xml +++ b/share/sgml/advisories.xml @@ -1,10 +1,10 @@ - + %includes; ]> - + &header; @@ -75,9 +75,9 @@ following releases of FreeBSD:

    At this time, security advisories are available for: @@ -222,7 +222,7 @@ condition and that the permissions are correct.
  • If an attacker can force packets to go/come from another arbitrary system then that attacker has complete control over the data that we get -and NONEof it should be trusted. +and NONE of it should be trusted.

  • Never trust a configuration file is correctly formatted or that it was @@ -262,7 +262,7 @@ suid/sgid program.
  • If you are unsure of your security fixes, send them to a reviewer with whom you have already arrangements for a second glance over your code. Don't commit code you are not sure about since breaking something -in the name of security fix is rather embarrassing. +in the name of a security fix is rather embarrassing.

  • Those without CVS commit privileges should make sure that a reviewer