betz Mon Jan 26 08:52:19 2004 EDT
Modified files:
/phpdoc/en/security index.xml intro.xml
Log:
split also the intro from index.xml. Thanks Goba
http://cvs.php.net/diff.php/phpdoc/en/security/index.xml?r1=1.67&r2=1.68&ty=u
Index: phpdoc/en/security/index.xml
diff -u phpdoc/en/security/index.xml:1.67 phpdoc/en/security/index.xml:1.68
--- phpdoc/en/security/index.xml:1.67 Mon Jan 26 08:22:25 2004
+++ phpdoc/en/security/index.xml Mon Jan 26 08:52:18 2004
@@ -1,44 +1,9 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.67 $ -->
+<!-- $Revision: 1.68 $ -->
<!-- Last Revision before split: 1.66 -->
<chapter id="security.index">
<title>Security</title>
-
- <simpara>
- PHP is a powerful language and the interpreter, whether included
- in a web server as a module or executed as a separate
- <acronym>CGI</acronym> binary, is able to access files, execute
- commands and open network connections on the server. These
- properties make anything run on a web server insecure by default.
- PHP is designed specifically to be a more secure language for
- writing CGI programs than Perl or C, and with correct selection of
- compile-time and runtime configuration options, and proper coding
- practices, it can give you exactly the combination of freedom and
- security you need.
- </simpara>
- <simpara>
- As there are many different ways of utilizing PHP, there are many
- configuration options controlling its behaviour. A large
- selection of options guarantees you can use PHP for a lot of
- purposes, but it also means there are combinations of these
- options and server configurations that result in an insecure
- setup.
- </simpara>
- <simpara>
- The configuration flexibility of PHP is equally rivalled by the
- code flexibility. PHP can be used to build complete server
- applications, with all the power of a shell user, or it can be used
- for simple server-side includes with little risk in a tightly
- controlled environment. How you build that environment, and how
- secure it is, is largely up to the PHP developer.
- </simpara>
- <simpara>
- This chapter starts with some general security advice, explains
- the different configuration option combinations and the situations
- they can be safely used, and describes different considerations in
- coding for different levels of security.
- </simpara>
-
+ &security.intro;
&security.general;
&security.cgi-bin;
&security.apache;
http://cvs.php.net/diff.php/phpdoc/en/security/intro.xml?r1=1.1&r2=1.2&ty=u
Index: phpdoc/en/security/intro.xml
diff -u phpdoc/en/security/intro.xml:1.1 phpdoc/en/security/intro.xml:1.2
--- phpdoc/en/security/intro.xml:1.1 Mon Jan 26 08:22:25 2004
+++ phpdoc/en/security/intro.xml Mon Jan 26 08:52:18 2004
@@ -1,3 +1,59 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.1 $ -->
+<!-- $Revision: 1.2 $ -->
<!-- splitted from ./index.xml, last change in rev 1.66 -->
+ <simpara>
+ PHP is a powerful language and the interpreter, whether included
+ in a web server as a module or executed as a separate
+ <acronym>CGI</acronym> binary, is able to access files, execute
+ commands and open network connections on the server. These
+ properties make anything run on a web server insecure by default.
+ PHP is designed specifically to be a more secure language for
+ writing CGI programs than Perl or C, and with correct selection of
+ compile-time and runtime configuration options, and proper coding
+ practices, it can give you exactly the combination of freedom and
+ security you need.
+ </simpara>
+ <simpara>
+ As there are many different ways of utilizing PHP, there are many
+ configuration options controlling its behaviour. A large
+ selection of options guarantees you can use PHP for a lot of
+ purposes, but it also means there are combinations of these
+ options and server configurations that result in an insecure
+ setup.
+ </simpara>
+ <simpara>
+ The configuration flexibility of PHP is equally rivalled by the
+ code flexibility. PHP can be used to build complete server
+ applications, with all the power of a shell user, or it can be used
+ for simple server-side includes with little risk in a tightly
+ controlled environment. How you build that environment, and how
+ secure it is, is largely up to the PHP developer.
+ </simpara>
+ <simpara>
+ This chapter starts with some general security advice, explains
+ the different configuration option combinations and the situations
+ they can be safely used, and describes different considerations in
+ coding for different levels of security.
+ </simpara>
+
+
+<!-- Keep this comment at the end of the file
+Local variables:
+mode: sgml
+sgml-omittag:t
+sgml-shorttag:t
+sgml-minimize-attributes:nil
+sgml-always-quote-attributes:t
+sgml-indent-step:1
+sgml-indent-data:t
+indent-tabs-mode:nil
+sgml-parent-document:nil
+sgml-default-dtd-file:"../../manual.ced"
+sgml-exposed-tags:nil
+sgml-local-catalogs:nil
+sgml-local-ecat-files:nil
+End:
+vim600: syn=xml fen fdm=syntax fdl=2 si
+vim: et tw=78 syn=sgml
+vi: ts=1 sw=1
+-->
