From 80d71116c11ba7ff90641a6693b025aa07804fbd Mon Sep 17 00:00:00 2001 From: Wolfram Schneider Date: Fri, 19 Jun 1998 09:46:53 +0000 Subject: [PATCH] The new FreeBSD Security homepage. Submitted by: guido --- data/security/Makefile | 12 ++ data/security/programmers.html | 205 +++++++++++++++++++++++++++++++++ data/security/secure.sgml | 60 ++++++++++ data/security/security.sgml | 166 ++++++++++++++++++++++++++ en/security/Makefile | 12 ++ en/security/advisories.xml | 166 ++++++++++++++++++++++++++ en/security/programmers.html | 205 +++++++++++++++++++++++++++++++++ en/security/secure.sgml | 60 ++++++++++ en/security/security.sgml | 166 ++++++++++++++++++++++++++ share/sgml/advisories.xml | 166 ++++++++++++++++++++++++++ 10 files changed, 1218 insertions(+) create mode 100644 data/security/Makefile create mode 100644 data/security/programmers.html create mode 100644 data/security/secure.sgml create mode 100644 data/security/security.sgml create mode 100644 en/security/Makefile create mode 100644 en/security/advisories.xml create mode 100644 en/security/programmers.html create mode 100644 en/security/secure.sgml create mode 100644 en/security/security.sgml create mode 100644 share/sgml/advisories.xml diff --git a/data/security/Makefile b/data/security/Makefile new file mode 100644 index 0000000000..947ceb0607 --- /dev/null +++ b/data/security/Makefile @@ -0,0 +1,12 @@ +# $Id: Makefile,v 1.1 1998-06-19 09:46:48 wosch Exp $ + +.if exists(Makefile.conf) +.include "Makefile.conf" +.endif + +DOCS= +DOCS+= programmers.sgml +DOCS+= security.sgml +DOCS+= secure.sgml + +.include "../web.mk" diff --git a/data/security/programmers.html b/data/security/programmers.html new file mode 100644 index 0000000000..ed31c0d3d8 --- /dev/null +++ b/data/security/programmers.html @@ -0,0 +1,205 @@ + + + +Security Do's and Don'ts for Programmers + +Navigation Bar +

Security Do's and Don'ts for Programmers


+ + + +Top +Applications +Support +Documentation +Vendors +Search +Index +Top +Top + + + +

+ +
+
questions@FreeBSD.ORG
+ Copyright © 1995-1998 FreeBSD Inc. + All rights reserved.
$Date: 1998-06-19 09:46:50 $
+ diff --git a/data/security/secure.sgml b/data/security/secure.sgml new file mode 100644 index 0000000000..58248fcafb --- /dev/null +++ b/data/security/secure.sgml @@ -0,0 +1,60 @@ + + + + %includes; +]> + + + + &header; + + +There are several steps involved in securing a FreeBSD system, or in +fact any UNIX system: + + + &footer + + diff --git a/data/security/security.sgml b/data/security/security.sgml new file mode 100644 index 0000000000..cd7ecd5c31 --- /dev/null +++ b/data/security/security.sgml @@ -0,0 +1,166 @@ + + + + %includes; +]> + + + + &header; + +

This guide attempts to document some of the tips and tricks used by +many FreeBSD security experts for securing systems and writing secure +code. It is designed to help you learn about the various ways of protecting +a FreeBSD system against outside attacks and how to recover from such attacks +if and when they should happen. It also lists the various ways in which +the systems programmer can become more security conscious so he will + less likely introduce security holes in the first place. + +

We welcome your comments on the contents and correctness of this page. +Please send email to the +FreeBSD Security Officers if you have changes you'd like to see here. + +

The FreeBSD security officer

+ +As FreeBSD takes security seriously, there is a security officer who is +the focal point for security related communications. The security officers' +main task is to send out advisories when there are known security holes +so FreeBSD users will be able to keep their systems secure. The security +officer also communicates with the various CERTs around the world to +give them information about vulnerabilities within FreeBSD and to receive +information about new ones. As such, the security officer is a member of +FIRST, the Forum of Incident Response +and Security Teams. +

+When you contact the security officer about sensitive matters, please use +our PGP key to encrypt your +message. + +

FreeBSD security related information

+If you want to stay up to date on FreeBSD security, you can subscribe +yorself to one of the following mailing lists: + +
+freebsd-security		General security related discussion
+freebsd-security-notification	Security notifications (moderated mailing list)
+
+ +Send mail to majordomo@FreeBSD.ORG +with +
+     subscribe <listname>  [<optional address>]
+
+in the body of the message in order to subscribe yourself. +

+Publications of the FreeBSD security officer can also be found on +ftp://ftp.freebsd.org/pub/CERT/ +

Handbook? + +

FreeBSD security advisories:

+FreeBSD provides security advisories. The advisories will cover +recent releases of FreeBSD. The security advisories will cover +these releases: + + +At this time, security advisories are available for: + + +Older releases will not be actively maintained. +

+You are encouraged to upgrade to one of the supported releases. +

+An advisory will be sent out when a security hole exists that is either being +actively abused (as indicated to us via reports from end users or CERT +like organizations), or when the security hole is public knowledge +(e.g. because a report has been posted to a public mailing list). +

+Like all development efforts, security fixes are first brought into the +FreeBSD-current branch. After a couple of days, the fix will be retrofitted +into the covered FreeBSD-stable branch(es). Then an advisory will +be sent out. +

+Advisories will be sent to the following FreeBSD mailing lists: +

+Advisories will always be signed using the FreeBSD security-officer +PGP key +

+Advisories and patches are archived at our +FTP site. + +

+ + + + + +

What to do when you detect a security compromise

+ + +Other questions you may ask yourself are: + + +

How to secure a FreeBSD system

+There are several steps involved in securing a FreeBSD system, or in +fact any UNIX system. + +

Security Do's and Don'ts for Programmers

+ + + +

Other usefull security information:

+ + + &footer + + diff --git a/en/security/Makefile b/en/security/Makefile new file mode 100644 index 0000000000..947ceb0607 --- /dev/null +++ b/en/security/Makefile @@ -0,0 +1,12 @@ +# $Id: Makefile,v 1.1 1998-06-19 09:46:48 wosch Exp $ + +.if exists(Makefile.conf) +.include "Makefile.conf" +.endif + +DOCS= +DOCS+= programmers.sgml +DOCS+= security.sgml +DOCS+= secure.sgml + +.include "../web.mk" diff --git a/en/security/advisories.xml b/en/security/advisories.xml new file mode 100644 index 0000000000..36e3f42d42 --- /dev/null +++ b/en/security/advisories.xml @@ -0,0 +1,166 @@ + + + + %includes; +]> + + + + &header; + +

This guide attempts to document some of the tips and tricks used by +many FreeBSD security experts for securing systems and writing secure +code. It is designed to help you learn about the various ways of protecting +a FreeBSD system against outside attacks and how to recover from such attacks +if and when they should happen. It also lists the various ways in which +the systems programmer can become more security conscious so he will + less likely introduce security holes in the first place. + +

We welcome your comments on the contents and correctness of this page. +Please send email to the +FreeBSD Security Officers if you have changes you'd like to see here. + +

The FreeBSD security officer

+ +As FreeBSD takes security seriously, there is a security officer who is +the focal point for security related communications. The security officers' +main task is to send out advisories when there are known security holes +so FreeBSD users will be able to keep their systems secure. The security +officer also communicates with the various CERTs around the world to +give them information about vulnerabilities within FreeBSD and to receive +information about new ones. As such, the security officer is a member of +FIRST, the Forum of Incident Response +and Security Teams. +

+When you contact the security officer about sensitive matters, please use +our PGP key to encrypt your +message. + +

FreeBSD security related information

+If you want to stay up to date on FreeBSD security, you can subscribe +yorself to one of the following mailing lists: + +
+freebsd-security		General security related discussion
+freebsd-security-notification	Security notifications (moderated mailing list)
+
+ +Send mail to majordomo@FreeBSD.ORG +with +
+     subscribe <listname>  [<optional address>]
+
+in the body of the message in order to subscribe yourself. +

+Publications of the FreeBSD security officer can also be found on +ftp://ftp.freebsd.org/pub/CERT/ +

Handbook? + +

FreeBSD security advisories:

+FreeBSD provides security advisories. The advisories will cover +recent releases of FreeBSD. The security advisories will cover +these releases: + + +At this time, security advisories are available for: + + +Older releases will not be actively maintained. +

+You are encouraged to upgrade to one of the supported releases. +

+An advisory will be sent out when a security hole exists that is either being +actively abused (as indicated to us via reports from end users or CERT +like organizations), or when the security hole is public knowledge +(e.g. because a report has been posted to a public mailing list). +

+Like all development efforts, security fixes are first brought into the +FreeBSD-current branch. After a couple of days, the fix will be retrofitted +into the covered FreeBSD-stable branch(es). Then an advisory will +be sent out. +

+Advisories will be sent to the following FreeBSD mailing lists: +

+Advisories will always be signed using the FreeBSD security-officer +PGP key +

+Advisories and patches are archived at our +FTP site. + +

+ + + + + +

What to do when you detect a security compromise

+ + +Other questions you may ask yourself are: + + +

How to secure a FreeBSD system

+There are several steps involved in securing a FreeBSD system, or in +fact any UNIX system. + +

Security Do's and Don'ts for Programmers

+ + + +

Other usefull security information:

+ + + &footer + + diff --git a/en/security/programmers.html b/en/security/programmers.html new file mode 100644 index 0000000000..ed31c0d3d8 --- /dev/null +++ b/en/security/programmers.html @@ -0,0 +1,205 @@ + + + +Security Do's and Don'ts for Programmers + +Navigation Bar +

Security Do's and Don'ts for Programmers


+ + + +Top +Applications +Support +Documentation +Vendors +Search +Index +Top +Top + + + +

+ +
+
questions@FreeBSD.ORG
+ Copyright © 1995-1998 FreeBSD Inc. + All rights reserved.
$Date: 1998-06-19 09:46:50 $
+ diff --git a/en/security/secure.sgml b/en/security/secure.sgml new file mode 100644 index 0000000000..58248fcafb --- /dev/null +++ b/en/security/secure.sgml @@ -0,0 +1,60 @@ + + + + %includes; +]> + + + + &header; + + +There are several steps involved in securing a FreeBSD system, or in +fact any UNIX system: + + + &footer + + diff --git a/en/security/security.sgml b/en/security/security.sgml new file mode 100644 index 0000000000..cd7ecd5c31 --- /dev/null +++ b/en/security/security.sgml @@ -0,0 +1,166 @@ + + + + %includes; +]> + + + + &header; + +

This guide attempts to document some of the tips and tricks used by +many FreeBSD security experts for securing systems and writing secure +code. It is designed to help you learn about the various ways of protecting +a FreeBSD system against outside attacks and how to recover from such attacks +if and when they should happen. It also lists the various ways in which +the systems programmer can become more security conscious so he will + less likely introduce security holes in the first place. + +

We welcome your comments on the contents and correctness of this page. +Please send email to the +FreeBSD Security Officers if you have changes you'd like to see here. + +

The FreeBSD security officer

+ +As FreeBSD takes security seriously, there is a security officer who is +the focal point for security related communications. The security officers' +main task is to send out advisories when there are known security holes +so FreeBSD users will be able to keep their systems secure. The security +officer also communicates with the various CERTs around the world to +give them information about vulnerabilities within FreeBSD and to receive +information about new ones. As such, the security officer is a member of +FIRST, the Forum of Incident Response +and Security Teams. +

+When you contact the security officer about sensitive matters, please use +our PGP key to encrypt your +message. + +

FreeBSD security related information

+If you want to stay up to date on FreeBSD security, you can subscribe +yorself to one of the following mailing lists: + +
+freebsd-security		General security related discussion
+freebsd-security-notification	Security notifications (moderated mailing list)
+
+ +Send mail to majordomo@FreeBSD.ORG +with +
+     subscribe <listname>  [<optional address>]
+
+in the body of the message in order to subscribe yourself. +

+Publications of the FreeBSD security officer can also be found on +ftp://ftp.freebsd.org/pub/CERT/ +

Handbook? + +

FreeBSD security advisories:

+FreeBSD provides security advisories. The advisories will cover +recent releases of FreeBSD. The security advisories will cover +these releases: + + +At this time, security advisories are available for: + + +Older releases will not be actively maintained. +

+You are encouraged to upgrade to one of the supported releases. +

+An advisory will be sent out when a security hole exists that is either being +actively abused (as indicated to us via reports from end users or CERT +like organizations), or when the security hole is public knowledge +(e.g. because a report has been posted to a public mailing list). +

+Like all development efforts, security fixes are first brought into the +FreeBSD-current branch. After a couple of days, the fix will be retrofitted +into the covered FreeBSD-stable branch(es). Then an advisory will +be sent out. +

+Advisories will be sent to the following FreeBSD mailing lists: +

+Advisories will always be signed using the FreeBSD security-officer +PGP key +

+Advisories and patches are archived at our +FTP site. + +

+ + + + + +

What to do when you detect a security compromise

+ + +Other questions you may ask yourself are: + + +

How to secure a FreeBSD system

+There are several steps involved in securing a FreeBSD system, or in +fact any UNIX system. + +

Security Do's and Don'ts for Programmers

+ + + +

Other usefull security information:

+ + + &footer + + diff --git a/share/sgml/advisories.xml b/share/sgml/advisories.xml new file mode 100644 index 0000000000..36e3f42d42 --- /dev/null +++ b/share/sgml/advisories.xml @@ -0,0 +1,166 @@ + + + + %includes; +]> + + + + &header; + +

This guide attempts to document some of the tips and tricks used by +many FreeBSD security experts for securing systems and writing secure +code. It is designed to help you learn about the various ways of protecting +a FreeBSD system against outside attacks and how to recover from such attacks +if and when they should happen. It also lists the various ways in which +the systems programmer can become more security conscious so he will + less likely introduce security holes in the first place. + +

We welcome your comments on the contents and correctness of this page. +Please send email to the +FreeBSD Security Officers if you have changes you'd like to see here. + +

The FreeBSD security officer

+ +As FreeBSD takes security seriously, there is a security officer who is +the focal point for security related communications. The security officers' +main task is to send out advisories when there are known security holes +so FreeBSD users will be able to keep their systems secure. The security +officer also communicates with the various CERTs around the world to +give them information about vulnerabilities within FreeBSD and to receive +information about new ones. As such, the security officer is a member of +FIRST, the Forum of Incident Response +and Security Teams. +

+When you contact the security officer about sensitive matters, please use +our PGP key to encrypt your +message. + +

FreeBSD security related information

+If you want to stay up to date on FreeBSD security, you can subscribe +yorself to one of the following mailing lists: + +
+freebsd-security		General security related discussion
+freebsd-security-notification	Security notifications (moderated mailing list)
+
+ +Send mail to majordomo@FreeBSD.ORG +with +
+     subscribe <listname>  [<optional address>]
+
+in the body of the message in order to subscribe yourself. +

+Publications of the FreeBSD security officer can also be found on +ftp://ftp.freebsd.org/pub/CERT/ +

Handbook? + +

FreeBSD security advisories:

+FreeBSD provides security advisories. The advisories will cover +recent releases of FreeBSD. The security advisories will cover +these releases: + + +At this time, security advisories are available for: + + +Older releases will not be actively maintained. +

+You are encouraged to upgrade to one of the supported releases. +

+An advisory will be sent out when a security hole exists that is either being +actively abused (as indicated to us via reports from end users or CERT +like organizations), or when the security hole is public knowledge +(e.g. because a report has been posted to a public mailing list). +

+Like all development efforts, security fixes are first brought into the +FreeBSD-current branch. After a couple of days, the fix will be retrofitted +into the covered FreeBSD-stable branch(es). Then an advisory will +be sent out. +

+Advisories will be sent to the following FreeBSD mailing lists: +

+Advisories will always be signed using the FreeBSD security-officer +PGP key +

+Advisories and patches are archived at our +FTP site. + +

+ + + + + +

What to do when you detect a security compromise

+ + +Other questions you may ask yourself are: + + +

How to secure a FreeBSD system

+There are several steps involved in securing a FreeBSD system, or in +fact any UNIX system. + +

Security Do's and Don'ts for Programmers

+ + + +

Other usefull security information:

+ + + &footer + +