os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add FreeBSD 3.{1,2} and remove FreeBSD 3.0 and FreeBSD 2.2.7 out

Browse source 
of the supported security advisory page.

Also, make a grammar change and a sgml nit while I'm here.
This commit is contained in:
Bill Fumerola 1999-05-31 01:30:40 +00:00
parent b2841d3618
commit 35c9348ef7
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=4981
3 changed files with 18 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

12
en/security/advisories.xml
View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-03-27 15:43:51 $">
<!ENTITY date "$Date: 1999-05-31 01:30:40 $">
<!ENTITY title "FreeBSD Security Information">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: advisories.xml,v 1.11 1999-03-27 15:43:51 nik Exp $ -->
<!-- $Id: advisories.xml,v 1.12 1999-05-31 01:30:40 billf Exp $ -->
<html>
&header;
@ -75,9 +75,9 @@ following releases of FreeBSD:</P>
At this time, security advisories are available for:
<UL>
<LI> FreeBSD 2.2.7
<LI> FreeBSD 2.2.8
<LI> FreeBSD 3.0
<LI> FreeBSD 3.1
<LI> FreeBSD 3.2
<LI> FreeBSD-current
<LI> FreeBSD-stable
</UL>
@ -222,7 +222,7 @@ condition and that the permissions are correct.
<LI>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 <B>NONE</B>of it should be trusted.
and <B>NONE</B> of it should be trusted.
<P></P></LI>
<LI>Never trust a configuration file is correctly formatted or that it was
@ -262,7 +262,7 @@ suid/sgid program.
<LI>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.
<P></P></LI>
<LI>Those without CVS commit privileges should make sure that a reviewer

12
en/security/security.sgml
View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-03-27 15:43:51 $">
<!ENTITY date "$Date: 1999-05-31 01:30:40 $">
<!ENTITY title "FreeBSD Security Information">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: security.sgml,v 1.11 1999-03-27 15:43:51 nik Exp $ -->
<!-- $Id: security.sgml,v 1.12 1999-05-31 01:30:40 billf Exp $ -->
<html>
&header;
@ -75,9 +75,9 @@ following releases of FreeBSD:</P>
At this time, security advisories are available for:
<UL>
<LI> FreeBSD 2.2.7
<LI> FreeBSD 2.2.8
<LI> FreeBSD 3.0
<LI> FreeBSD 3.1
<LI> FreeBSD 3.2
<LI> FreeBSD-current
<LI> FreeBSD-stable
</UL>
@ -222,7 +222,7 @@ condition and that the permissions are correct.
<LI>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 <B>NONE</B>of it should be trusted.
and <B>NONE</B> of it should be trusted.
<P></P></LI>
<LI>Never trust a configuration file is correctly formatted or that it was
@ -262,7 +262,7 @@ suid/sgid program.
<LI>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.
<P></P></LI>
<LI>Those without CVS commit privileges should make sure that a reviewer

12
share/sgml/advisories.xml
View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$Date: 1999-03-27 15:43:51 $">
<!ENTITY date "$Date: 1999-05-31 01:30:40 $">
<!ENTITY title "FreeBSD Security Information">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $Id: advisories.xml,v 1.11 1999-03-27 15:43:51 nik Exp $ -->
<!-- $Id: advisories.xml,v 1.12 1999-05-31 01:30:40 billf Exp $ -->
<html>
&header;
@ -75,9 +75,9 @@ following releases of FreeBSD:</P>
At this time, security advisories are available for:
<UL>
<LI> FreeBSD 2.2.7
<LI> FreeBSD 2.2.8
<LI> FreeBSD 3.0
<LI> FreeBSD 3.1
<LI> FreeBSD 3.2
<LI> FreeBSD-current
<LI> FreeBSD-stable
</UL>
@ -222,7 +222,7 @@ condition and that the permissions are correct.
<LI>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 <B>NONE</B>of it should be trusted.
and <B>NONE</B> of it should be trusted.
<P></P></LI>
<LI>Never trust a configuration file is correctly formatted or that it was
@ -262,7 +262,7 @@ suid/sgid program.
<LI>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.
<P></P></LI>
<LI>Those without CVS commit privileges should make sure that a reviewer