diff --git a/en/docproj/who.sgml b/en/docproj/who.sgml index 26e17d9cca..0eb1841286 100644 --- a/en/docproj/who.sgml +++ b/en/docproj/who.sgml @@ -1,32 +1,32 @@ - + %includes; ]> - + &header;

The project is a fairly loosely knit group of people, and the only thing we have got in common is that we are subscribed to the mailing list FreeBSD-doc@FreeBSD.ORG.

Some of us can commit changes directly to the FreeBSD documentation tree. The complete list of people with commit ``privs'' is in the + href="../handbook/staff:doc.html">the Handbook.

Others do not have commit privs, but they write and submit documentation nonetheless. One of the committers will then include it in the documentation set.

If you want to help out with the documentation project (and I fervently hope you do) all you have to do is subscribe to the mailing list and participate. As soon as you have done that you're a member of the project.

&footer diff --git a/en/news/qnewsletter-1-3.sgml b/en/news/qnewsletter-1-3.sgml index 52ed8a374d..e3cfec0852 100644 --- a/en/news/qnewsletter-1-3.sgml +++ b/en/news/qnewsletter-1-3.sgml @@ -1,108 +1,108 @@ - + %includes; ]> - + &header;

FreeBSD Really-Quick(TM) NewsLetter.
Things Happening in FreeBSD.
Volume #1 Issue #3
July 1998

This is an (at least) monthly Newsletter, published only by E-mail. If you have anything you would like to see in the next edition, please send e-mail to fbsd-book@vmunix.com

-Chris Coleman <chrisc@vmunix.com>

Previous Quick Newsletter &footer; diff --git a/en/projects/newbies.sgml b/en/projects/newbies.sgml index a8fa23f1d4..355b5065c1 100644 --- a/en/projects/newbies.sgml +++ b/en/projects/newbies.sgml @@ -1,254 +1,254 @@ - + %includes; ]> - + &header;

The following resources are some of those which FreeBSD newbies have found most helpful when learning to use FreeBSD. Please send corrections and additions to FreeBSD-Newbies@FreeBSD.org.

Using the FreeBSD web site

This web site is the main source of up to date information about FreeBSD. Newbies have found the following pages particularly helpful:

Learning about FreeBSD

Learning about UNIX

Many of the problems we have as newbies come from being unfamiliar with the UNIX commands needed to fix our FreeBSD problems. Without a UNIX background you'll be faced with two things to learn at once. Fortunately a lot of resources are available to make this easier.

Learning about the X Window System

The X Window System is used with a number of operating systems, including FreeBSD. The documentation for X can be found at The XFree86 Project, Inc., including the XFree86 FAQ. Beware, much of this documentation is reference material which is likely to be difficult for newcomers to digest.

Helping other people

Everyone has something to contribute to the FreeBSD community, even newbies! Some are busy working with the new advocacy group and some have become involved with the Documentation Project as reviewers. Other FreeBSD newbies might have particular skills and experiences to share, either computer related or not, or just want to meet new newbies and make them feel welcome. There's always people around who help others simply because they like to. Write to FreeBSD Newbies for more information.

Friends who run FreeBSD are a great resource. No book can replace chatting on the phone or across a pizza with someone who has the same interests, enjoys similar accomplishments, and faces the same challenges. If you don't have many friends who use FreeBSD, consider using your old FreeBSD CDs to create some more :-)

User groups are good places to meet other FreeBSD users. If there's not one nearby, maybe you could start one.

Before talking to real humans about your new skills, you might want to check the Pronunciation Guide and the Jargon File :-)

On line we have the FreeBSD-Newbies mailing list for non-technical discussions about matters of interest to newbies. Another mailing list, FreeBSD-Questions, answers our questions about using FreeBSD.

&footer; diff --git a/en/security/advisories.xml b/en/security/advisories.xml index be6cf68911..e7618d66cd 100644 --- a/en/security/advisories.xml +++ b/en/security/advisories.xml @@ -1,206 +1,206 @@ - + %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

FreeBSD takes security seriously, a dedicated team of security officers providing a focal point for security related communications. A security officers' main task is to send out advisories when there are known security holes and otherwise keep abreast of security issues. The security officers also communicate with the various CERT and FIRST teams around the world, sharing information about vulnerabilities in FreeBSD or utilities commonly used by FreeBSD, and keeping up to date on security issues in the world at large. The security officers are also active members of those organizations.

When you need to contact the security officers about a sensitive matter, please use their PGP key to encrypt your message before sending it.

FreeBSD security advisories:

The FreeBSD security officers provide security advisories for the following releases of FreeBSD:

At this time, security advisories are available for:

Older releases will not be actively maintained and users are strongly 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 +the FreeBSD-current branch. 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 always signed using the FreeBSD security officer PGP key and are archived, along with their associated patches, at our FTP CERT repository. At the time of this writing, the following advisories are currently available:

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.

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 useful security information:

&footer diff --git a/en/security/security.sgml b/en/security/security.sgml index 2b03534fab..57a9d92946 100644 --- a/en/security/security.sgml +++ b/en/security/security.sgml @@ -1,206 +1,206 @@ - + %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

FreeBSD takes security seriously, a dedicated team of security officers providing a focal point for security related communications. A security officers' main task is to send out advisories when there are known security holes and otherwise keep abreast of security issues. The security officers also communicate with the various CERT and FIRST teams around the world, sharing information about vulnerabilities in FreeBSD or utilities commonly used by FreeBSD, and keeping up to date on security issues in the world at large. The security officers are also active members of those organizations.

When you need to contact the security officers about a sensitive matter, please use their PGP key to encrypt your message before sending it.

FreeBSD security advisories:

The FreeBSD security officers provide security advisories for the following releases of FreeBSD:

At this time, security advisories are available for:

Older releases will not be actively maintained and users are strongly 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 +the FreeBSD-current branch. 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 always signed using the FreeBSD security officer PGP key and are archived, along with their associated patches, at our FTP CERT repository. At the time of this writing, the following advisories are currently available:

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.

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 useful security information:

&footer diff --git a/share/sgml/advisories.xml b/share/sgml/advisories.xml index be6cf68911..e7618d66cd 100644 --- a/share/sgml/advisories.xml +++ b/share/sgml/advisories.xml @@ -1,206 +1,206 @@ - + %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

FreeBSD takes security seriously, a dedicated team of security officers providing a focal point for security related communications. A security officers' main task is to send out advisories when there are known security holes and otherwise keep abreast of security issues. The security officers also communicate with the various CERT and FIRST teams around the world, sharing information about vulnerabilities in FreeBSD or utilities commonly used by FreeBSD, and keeping up to date on security issues in the world at large. The security officers are also active members of those organizations.

When you need to contact the security officers about a sensitive matter, please use their PGP key to encrypt your message before sending it.

FreeBSD security advisories:

The FreeBSD security officers provide security advisories for the following releases of FreeBSD:

At this time, security advisories are available for:

Older releases will not be actively maintained and users are strongly 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 +the FreeBSD-current branch. 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 always signed using the FreeBSD security officer PGP key and are archived, along with their associated patches, at our FTP CERT repository. At the time of this writing, the following advisories are currently available:

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.

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 useful security information:

&footer