From owner-p4-projects@FreeBSD.ORG Thu Jul 24 14:50:47 2008 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 3DABA106567F; Thu, 24 Jul 2008 14:50:47 +0000 (UTC) Delivered-To: perforce@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2F381065670 for ; Thu, 24 Jul 2008 14:50:46 +0000 (UTC) (envelope-from remko@freebsd.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id F0FC48FC08 for ; Thu, 24 Jul 2008 14:50:46 +0000 (UTC) (envelope-from remko@freebsd.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.2/8.14.2) with ESMTP id m6OEokaG063568 for ; Thu, 24 Jul 2008 14:50:46 GMT (envelope-from remko@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.2/8.14.1/Submit) id m6OEoh0a063562 for perforce@freebsd.org; Thu, 24 Jul 2008 14:50:43 GMT (envelope-from remko@freebsd.org) Date: Thu, 24 Jul 2008 14:50:43 GMT Message-Id: <200807241450.m6OEoh0a063562@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to remko@freebsd.org using -f From: Remko Lodder To: Perforce Change Reviews Cc: Subject: PERFORCE change 145813 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2008 14:50:47 -0000 http://perforce.freebsd.org/chv.cgi?CH=145813 Change 145813 by remko@remko_nakur on 2008/07/24 14:50:32 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/mailing-lists.ent#4 integrate .. //depot/projects/docproj_nl/share/pgpkeys/glarkin.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/pgollucci.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#5 integrate .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#5 integrate .. //depot/projects/docproj_nl/share/pgpkeys/rnoland.key#1 branch .. //depot/projects/docproj_nl/share/sgml/mirrors.xml#2 integrate .. //depot/projects/docproj_nl/www/en/cgi/cvsweb.conf#2 integrate .. //depot/projects/docproj_nl/www/en/developers.sgml#3 integrate .. //depot/projects/docproj_nl/www/en/developers/cvs.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/donations/donors.sgml#3 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#4 integrate .. //depot/projects/docproj_nl/www/share/sgml/press.xml#3 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#3 (text+ko) ==== @@ -13,7 +13,7 @@ - $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.275 2008/06/20 00:28:50 erwin Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.276 2008/07/22 17:05:47 remko Exp $ 1999 @@ -107,7 +107,7 @@ Core Team monthly reports - /home/core/public/monthly-report + /home/core/public/monthly-reports on the FreeBSD.org cluster. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#3 (text+ko) ==== @@ -1,4 +1,4 @@ - + + @@ -56,20 +56,6 @@ Perl and Python have I18N and wide character handling libraries. Please use them for I18N compliance. - - In older FreeBSD versions, - Perl may give warnings about not having a wide character locale - installed on your system. You can set the - environment variable LD_PRELOAD to - /usr/lib/libxpg4.so in your shell. - - In sh-based shells: - - LD_PRELOAD=/usr/lib/libxpg4.so - - In C-based shells: - - setenv LD_PRELOAD /usr/lib/libxpg4.so ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml#2 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -57,13 +57,7 @@ Morris Internet worm - effective today. Of the 17 CERT security advisories of 1999, 10 - - - CERTsecurity advisories - - - of them were directly caused by buffer-overflow software bugs. + effective today. By far the most common type of buffer overflow attack is based on corrupting the stack. @@ -258,40 +252,32 @@ Unfortunately there is still a very large assortment of code in public use which blindly copies memory around without using any of the bounded copy routines we just discussed. - Fortunately, there is another solution. Several compiler - add-ons and libraries exist to do Run-time bounds checking in - C/C++. + Fortunately, there is a way to help prevent such attacks — + run-time bounds checking, which is implemented by several + C/C++ compilers. + ProPolice StackGuard gcc - StackGuard is one such add-on that is implemented as a - small patch to the gcc code generator. From the StackGuard - website: + ProPolice is one such compiler feature, and is integrated + into &man.gcc.1; versions 4.1 and later. It replaces and + extends the earlier StackGuard &man.gcc.1; extension. -
"StackGuard detects and defeats stack - smashing attacks by protecting the return address on the stack - from being altered. StackGuard places a "canary" word next to - the return address when a function is called. If the canary - word has been altered when the function returns, then a stack - smashing attack has been attempted, and the program responds - by emitting an intruder alert into syslog, and then - halts."
- -
"StackGuard is implemented as a small patch - to the gcc code generator, specifically the function_prolog() - and function_epilog() routines. function_prolog() has been - enhanced to lay down canaries on the stack when functions - start, and function_epilog() checks canary integrity when the - function exits. Any attempt at corrupting the return address - is thus detected before the function - returns."
- + ProPolice helps to protect against stack-based buffer + overflows and other attacks by laying pseudo-random numbers in + key areas of the stack before calling any function. When a + function returns, these canaries are checked + and if they are found to have been changed the executable is + immediately aborted. Thus any attempt to modify the return + address or other variable stored on the stack in an attempt to + get malicious code to run is unlikely to succeed, as the + attacker would have to also manage to leave the pseudo-random + canaries untouched. buffer overflow - Recompiling your application with StackGuard is an + Recompiling your application with ProPolice is an effective means of stopping most buffer-overflow attacks, but it can still be compromised. @@ -378,7 +364,8 @@ should also be noted that a process can easily break out of a chroot environment if it has root privilege. This could be accomplished by creating device nodes to read kernel memory, - attaching a debugger to a process outside of the jail, or in + attaching a debugger to a process outside of the &man.chroot.8; + environment, or in many other creative ways. The behavior of the chroot() system ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml#2 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -138,10 +138,10 @@ The Bywater Basic Interpreter can be found in the Ports Collection as - lang/bwbasic + lang/bwbasic and the Phil Cockroft's Basic Interpreter (formerly Rabbit Basic) is available as - lang/pbasic. + lang/pbasic. @@ -163,14 +163,14 @@ Various implementations of Lisp that can run on &unix; systems are available in the Ports Collection for &os;. GNU Common Lisp can be found as - lang/gcl. CLISP + lang/gcl. CLISP by Bruno Haible and Michael Stoll is available as - lang/clisp. + lang/clisp. For CMUCL, which includes a highly-optimizing compiler too, or simpler Lisp implementations like SLisp, which implements most of the Common Lisp constructs in a few hundred lines of C code, - lang/cmucl and - lang/slisp are available + lang/cmucl and + lang/slisp are available respectively. @@ -184,7 +184,7 @@ writing CGI scripts. Perl is available in the Ports Collection as - lang/perl5 for all + lang/perl5 for all &os; releases, and is installed as /usr/bin/perl in the base system 4.X releases. @@ -201,12 +201,12 @@ abstraction to be used in research work. Scheme is available from the Ports Collection as - lang/elk for the + lang/elk for the Elk Scheme Interpreter. The MIT Scheme Interpreter can be found in - lang/mit-scheme + lang/mit-scheme and the SCM Scheme Interpreter in - lang/scm. + lang/scm. @@ -218,7 +218,7 @@ facilities for processing strings and structures. The version of Icon for &os; can be found in the Ports Collection as - lang/icon. + lang/icon. @@ -235,7 +235,7 @@ The latest version of Logo for &os; is available from the Ports Collection in - lang/logo. + lang/logo. @@ -253,7 +253,7 @@ The latest version of Python is available from the Ports Collection in - lang/python. + lang/python. @@ -268,7 +268,7 @@ programs. Ruby is available from the Ports Collection as - lang/ruby18. + lang/ruby18. @@ -285,7 +285,7 @@ Various versions of Tcl are available as ports for &os;. The latest version, Tcl 8.4, can be found in - lang/tcl84. + lang/tcl84. @@ -327,16 +327,16 @@ language to start with. FreeBSD does not include Pascal support in the base system, but both GNU Pascal Compiler (GPC) and the Free Pascal Compiler - are available in the ports collection as - lang/gpc and - lang/fpc. + are available in the Ports Collection as + lang/gpc and + lang/fpc. As the edit-compile-run-debug cycle is rather tedious when using separate programs, many commercial compiler makers have produced Integrated Development Environments (IDEs for short). FreeBSD does not include - an IDE in the base system, but devel/kdevelop is - available in the ports tree and many use + an IDE in the base system, but devel/kdevelop is + available in the Ports Collection and many use Emacs for this purpose. Using Emacs as an IDE is discussed in . @@ -1410,7 +1410,7 @@ &prompt.user; gdb progname - although most people prefer to run it inside + although many people prefer to run it inside Emacs. You can do this by: M-x gdb RET progname RET @@ -1430,9 +1430,9 @@ on a few of the basic commands. Finally, if you find its text-based command-prompt style - off-putting, there is a graphical front-end for it (xxgdb) in the ports - collection. + off-putting, there is a graphical front-end for it + (devel/xxgdb) in the Ports + Collection. This section is intended to be an introduction to using gdb and does not cover specialized topics @@ -1456,8 +1456,9 @@ At the gdb prompt, type break main. This will tell the - debugger to skip over the preliminary set-up code in the - program and start at the beginning of your code. Now type + debugger that you are not interested in watching the + preliminary set-up code in the program being run, and that it + should stop execution at the beginning of your code. Now type run to start the program—it will start at the beginning of the set-up code and then get stopped by the debugger when it calls main(). @@ -1681,7 +1682,7 @@ Some powerful, free IDEs now exist, such as KDevelop - in the ports collection. + in the Ports Collection. However, it is possible to set up your own environment. It @@ -1757,9 +1758,9 @@ And doubtless many more that I have overlooked. - Emacs can be installed on FreeBSD using the Emacs - port. + Emacs can be installed on &os; using + the editors/emacs + port. Once it is installed, start it up and do C-h t to read an Emacs tutorial—that means @@ -2234,7 +2235,7 @@ &prompt.user; find /usr/ports/lang/whizbang -name "*.el" -print and install them by copying them into the Emacs site Lisp - directory. On FreeBSD 2.1.0-RELEASE, this is + directory. On &os;, this is /usr/local/share/emacs/site-lisp. So for example, if the output from the find command ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#5 (text+ko) ==== @@ -6,11 +6,13 @@ - Frequently Asked Questions for &os; 6.<replaceable>X</replaceable> and 7.<replaceable>X</replaceable> + Frequently Asked Questions for &os; + 6.<replaceable>X</replaceable> and + 7.<replaceable>X</replaceable> The &os; Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1073 2008/07/14 00:11:44 pgj Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1077 2008/07/23 21:32:46 pgj Exp $ 1995 @@ -57,27 +59,30 @@ - This is the FAQ for &os; versions 6.X and 7.X. - All entries are assumed to be relevant to &os; 6.X and - later, unless otherwise noted. If you are interested in - helping with this project, send email to the &a.doc;. The - latest version of this document is always available from the - &os; - World Wide Web server. It may also be downloaded as - one large HTML file with HTTP - or as plain text, &postscript;, PDF, etc. from the &os; FTP - server. You may also want to Search the - FAQ. + This is the FAQ for &os; versions + 6.X and + 7.X. All entries are assumed to be + relevant to &os; 6.X and later, + unless otherwise noted. If you are interested in helping with + this project, send email to the &a.doc;. The latest version of + this document is always available from the &os; World Wide Web server. + It may also be downloaded as one large HTML file with HTTP or as plain text, + &postscript;, PDF, etc. from the &os; FTP + server. You may also want to Search the FAQ. + Introduction - Welcome to the &os; 6.X-7.X FAQ! + Welcome to the &os; + 6.X-7.X + FAQ! As is usual with Usenet FAQs, this document aims to cover the most frequently asked questions concerning the &os; operating @@ -87,632 +92,644 @@ information resources. Every effort has been made to make this FAQ as informative as - possible; if you have any suggestions as to how it may be improved, - please feel free to mail them to the &a.doc;. + possible; if you have any suggestions as to how it may be + improved, please feel free to mail them to the &a.doc;. - - What is &os;? - + + What is &os;? + - - Briefly, &os; is a &unix; like operating system for - AMD64 and &intel; EM64T, &i386; PC-98, IA-64, &arm;, &powerpc; - and &ultrasparc; platforms - based on U.C. Berkeley's 4.4BSD-Lite - release, with some 4.4BSD-Lite2 - enhancements. It is also based indirectly on William - Jolitz's port of U.C. Berkeley's Net/2 to - the &i386;, known as 386BSD, though very - little of the 386BSD code remains. A fuller description of - what &os; is and how it can work for you may be found on - the &os; home - page. + + Briefly, &os; is a &unix; like operating system for + AMD64 and &intel; EM64T, &i386; PC-98, IA-64, &arm;, + &powerpc; and &ultrasparc; platforms based on U.C. + Berkeley's 4.4BSD-Lite release, with some + 4.4BSD-Lite2 enhancements. It is also based + indirectly on William Jolitz's port of U.C. Berkeley's + Net/2 to the &i386;, known as + 386BSD, though very little of the 386BSD code + remains. A fuller description of what &os; is and how it + can work for you may be found on the &os; home page. + - &os; is used by companies, Internet Service Providers, - researchers, computer professionals, students and home users - all over the world in their work, education and recreation. + &os; is used by companies, Internet Service Providers, + researchers, computer professionals, students and home users + all over the world in their work, education and + recreation. - For more detailed information on &os;, please see the - &os; - Handbook. - + For more detailed information on &os;, please see the + &os; Handbook. + + - - What is the goal of the &os; Project? - + + What is the goal of the &os; Project? + - - The goal of the &os; Project is to provide software - that may be used for any purpose and without strings attached. - Many of us have a significant investment in the code (and - project) and would certainly not mind a little financial - compensation now and then, but we definitely do not - insist on it. We believe that our first and foremost - mission is to provide code to any and all - comers, and for whatever purpose, so that the code gets the - widest possible use and provides the widest possible benefit. - This is, we believe, one of the most fundamental goals of Free - Software and one that we enthusiastically support. + + The goal of the &os; Project is to provide software that + may be used for any purpose and without strings attached. + Many of us have a significant investment in the code (and + project) and would certainly not mind a little financial + compensation now and then, but we definitely do not insist + on it. We believe that our first and foremost + mission is to provide code to any and all + comers, and for whatever purpose, so that the code gets the + widest possible use and provides the widest possible + benefit. This is, we believe, one of the most fundamental + goals of Free Software and one that we enthusiastically + support. - That code in our source tree which falls under the - GNU - General Public License (GPL) or GNU - Library General Public License (LGPL) comes with - slightly more strings attached, though at least on the - side of enforced access rather than the usual opposite. - Due to the additional complexities that can evolve in the - commercial use of GPL software, we do, however, endeavor - to replace such software with submissions under the more - relaxed - &os; license whenever possible. - + That code in our source tree which falls under the + GNU General Public License (GPL) + or GNU Library General Public License (LGPL) + comes with slightly more strings attached, though at least + on the side of enforced access rather than the usual + opposite. Due to the additional complexities that can + evolve in the commercial use of GPL software, we do, + however, endeavor to replace such software with submissions + under the more relaxed &os; license + whenever possible. + - - Does the &os; license have any restrictions? - + + Does the &os; license have any restrictions? + - - Yes. Those restrictions do not control how you use - the code, merely how you treat the &os; Project itself. - If you have serious license concerns, read the actual - - license. For the simply curious, the license can - be summarized like this. + + Yes. Those restrictions do not control how you use the + code, merely how you treat the &os; Project itself. If you + have serious license concerns, read the actual license. + For the simply curious, the license can be summarized like + this. - - - Do not claim that you wrote this. - + + + Do not claim that you wrote this. + - - Do not sue us if it breaks. - - - + + Do not sue us if it breaks. + + + >>> TRUNCATED FOR MAIL (1000 lines) <<<