cvs: /phpdoc/chapters security.sgml
| From: | Rasmus Lerdorf | Date: | Thu, 02 Sep 1999 15:20:27 +0000 |
| Subject: | cvs: /phpdoc/chapters security.sgml | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-10452@lists.php.net to get a copy of this message | ||
rasmus Thu Sep 2 11:20:27 1999 EDT
Modified files:
/phpdoc/chapters security.sgml
Log:
Fix the language here a bit
Index: phpdoc/chapters/security.sgml
diff -u phpdoc/chapters/security.sgml:1.2 phpdoc/chapters/security.sgml:1.3
--- phpdoc/chapters/security.sgml:1.2 Sat Jul 31 20:37:07 1999
+++ phpdoc/chapters/security.sgml Thu Sep 2 11:19:57 1999
@@ -36,7 +36,7 @@
installing executable PHP binary to the web server cgi-bin
directory. CERT advisory <ulink
url="http://www.cert.org/advisories/CA-96.11.interpreters_in_cgi_bin_dir.html">CA-96.11</ulink>
- recommends agains placing any interpreters into cgi-bin. Even
+ recommends against placing any interpreters into cgi-bin. Even
if the PHP binary can be used as a standalone interpreter, PHP
is designed to prevent the attacks this setup makes possible:
@@ -45,7 +45,7 @@
<filename role=url>http://my.host/cgi-bin/php?/etc/passwd</filename>
<simpara>
- The query information in an url after the question mark (?)
+ The query information in a url after the question mark (?)
is passed as command line arguments to the interpreter by the
CGI interface. Usually interpreters open and execute the
file specified as the first argument on the command line.
@@ -87,8 +87,8 @@
linkend="ini.doc-root">doc_root</link> and <link
linkend="ini.user-dir">user_dir</link> can be used to prevent
this attack, if the server document tree has any directories
- with access restrictions. See below for full explanation of
- different combinations.
+ with access restrictions. See below for full the explanation of
+ the different combinations.
</simpara></listitem>
</itemizedlist>
@@ -100,7 +100,7 @@
by password or ip based access control, there is no need for
these configuration options. If your web server does not allow
you to do redirects, or the server does not have a way to
- communicate with the PHP binary that the request is a safely
+ communicate to the PHP binary that the request is a safely
redirected request, you can specify the option <link
linkend="enable-force-cgi-redirect">--disable-force-cgi-redirect</link>
to the configure script. You still have to make sure your PHP
@@ -144,12 +144,12 @@
<simpara>
To include active content, like scripts and executables, in the
web server document directories is sometimes consider an
- insecure practice. If for some configuration mistake the
- scripts are not executed but displayed as usual HTML documents,
+ insecure practice. If, because of some configuration mistake, the
+ scripts are not executed but displayed as regular HTML documents,
this may result in leakage of intellectual property or security
information like passwords. Therefore many sysadmins will
prefer setting up another directory structure for scripts that
- is only accessible through the PHP CGI, and therefore always
+ are accessible only through the PHP CGI, and therefore always
interpreted and not displayed as such.
<simpara>