Update the list of security advisories for 2000, now that they have

finally appeared on the FTP site.

Update the list of FreeBSD releases for which security advisories are
released.

Make mention of the its4 port for security auditing.

Point to http://www.shmoo.com/securecode/ as a useful secure coding
reference site.
This commit is contained in:
Kris Kennaway 2000-05-09 06:23:16 +00:00
parent 75ee961c31
commit 3ad5d4f197
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=7177
3 changed files with 93 additions and 21 deletions

View file

@ -1,10 +1,10 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/security/security.sgml,v 1.22 2000/04/03 11:03:37 kuriyama Exp $">
<!ENTITY date "$FreeBSD: www/en/security/security.sgml,v 1.23 2000/04/13 02:36:50 kris Exp $">
<!ENTITY title "FreeBSD Security Information">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
]>
<!-- $FreeBSD: www/en/security/security.sgml,v 1.22 2000/04/03 11:03:37 kuriyama Exp $ -->
<!-- $FreeBSD: www/en/security/security.sgml,v 1.23 2000/04/13 02:36:50 kris Exp $ -->
<html>
&header;
@ -73,12 +73,12 @@ following releases of FreeBSD:</P>
have 2 releases based on it.</LI>
</UL>
At this time, security advisories are available for:
At this time, security advisories are being released for:
<UL>
<LI> FreeBSD 3.3</LI>
<LI> FreeBSD 3.4</LI>
<LI> FreeBSD-current</LI>
<LI> FreeBSD-stable</LI>
<LI> FreeBSD 3.4-STABLE</LI>
<LI> FreeBSD 4.0-RELEASE</LI>
<LI> FreeBSD 4.0-STABLE</LI>
<LI> FreeBSD 5.0-CURRENT</LI>
</UL>
<P>Older releases are not maintained and users are strongly encouraged
@ -106,6 +106,19 @@ repository</A>. At the time of this writing, the following advisories are
currently available:</P>
<UL>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:15-imap-uw.asc">FreeBSD-SA-00:15-imap-uw.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:14-imap-uw.asc">FreeBSD-SA-00:14-imap-uw.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:13-generic-nqs.asc">FreeBSD-SA-00:13-generic-nqs.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:12-healthd.asc">FreeBSD-SA-00:12-healthd.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:11-ircii.asc">FreeBSD-SA-00:11-ircii.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:10-orville-write.asc">FreeBSD-SA-00:10-orville-write.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:09-mtr.asc">FreeBSD-SA-00:09-mtr.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:08-lynx.asc">FreeBSD-SA-00:08-lynx.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:07-mh.asc">FreeBSD-SA-00:07-mh.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:06-htdig.asc">FreeBSD-SA-00:06-htdig.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:05-mysql.asc">FreeBSD-SA-00:05-mysql.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:04-delegate.asc">FreeBSD-SA-00:04-delegate.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:03-asmon.asc">FreeBSD-SA-00:03-asmon.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:02.procfs.asc">FreeBSD-SA-00:02.procfs.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-00:01.make.asc">FreeBSD-SA-00:01.make.asc</A></LI>
<LI><A HREF="ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-99:06.amd.asc">FreeBSD-SA-99:06.amd.asc</A></LI>
@ -345,6 +358,17 @@ routines, always set any file descriptors that you open to close-on-exec.
<P></P></LI>
</UL>
<P>A useful auditing tool is the its4 port, located in
/usr/ports/security/its4/. This is an automated C code auditor which
hilights potential trouble-spots in the code. It is a useful
first-pass tool, but should not be relied upon as being authoritative,
and a complete audit should include human examination of the entire
code.</P>
<P>For more information on secure programming techniques and resources, see
the <A HREF="http://www.shmoo.com/securecode/">How to Write Secure Code</A>
resource center.</P>
<A NAME=tat></A>
<H2>FreeBSD Security Tips and Tricks</H2>
<P>There are several steps one must take to secure a FreeBSD system, or