neale/homepage
neale
/
homepage
1
0
Fork 0
Code Pull Requests Actions Activity

More CSS twiddling

This commit is contained in:
Neale Pickett 2015-03-24 23:12:52 +00:00
parent e7b8fb87c2
commit 7438074515
3 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
css/format.css
View File

@ -1,5 +1,5 @@
body { body {
font-family: "URW Palladio L", serif; font-family: "DejaVu Serif", serif;
} }
p, li, dd { p, li, dd {
@ -10,7 +10,7 @@ body > p {
text-indent: 1.5em; text-indent: 1.5em;
} }
h1 + p, h2 + p, h3 + p, h4 + p, h5 + p, h6 + p { h1 + p, h2 + p, h3 + p, h4 + p, h5 + p, h6 + p, ol + p, ul + p, pre + p, blockquote + p, img + p {
text-indent: 0; text-indent: 0;
} }

2
css/print.css
View File

@ -8,7 +8,7 @@ pre {
border: solid black 1px; border: solid black 1px;
} }
a:link { a:link, a:visited {
color: inherit; color: inherit;
text-decoration: underline; text-decoration: underline;
} }

12
papers/php-cgi.mdwn
View File

@ -55,17 +55,17 @@ Now I get this (reformatted for narrow displays):
<a href="http://php.net/install.windows">the <a href="http://php.net/install.windows">the
manual page</a>.</p> manual page</a>.</p>
It's writing out HTML, sort of: I mean, the first paragraph doesn't have P tags, but whatever. It's writing out HTML, sort of: I mean, the first paragraph doesn't have `P` tags, but whatever.
So clearly they intend me to see it from a browser. So clearly they intend me to see it from a browser.
I mean, the interpreter binary is called `php-cgi`, after all. I mean, the interpreter binary is called `php-cgi`, after all.
And yet, they're not actually writing out a CGI header, And yet, they're not actually writing out a CGI header,
so the web server thinks it's a broken script and dies. so the web server thinks it's a broken script and dies.
So maybe they meant me to view this from the command-line. So maybe they meant me to view this from the command-line;
Except, this error only shows up when I run it as CGI. except the only way to get this error is to run it as CGI.
Anyway. Anyway.
PHP is asking me to set the REDIRECT_STATUS variable, PHP is asking me to set the `REDIRECT_STATUS` variable,
and telling me that this is somehow a security concern. and telling me that this is somehow a security concern.
It's interesting how Python, Perl, and Lua don't think the lack of this variable is a security problem. It's interesting how Python, Perl, and Lua don't think the lack of this variable is a security problem.
@ -100,7 +100,7 @@ given that PHP has sent its "X-Powered-By" header.
If it couldn't find the file, it wouldn't have known enough to start php-cgi. If it couldn't find the file, it wouldn't have known enough to start php-cgi.
And, remember, this all works fine from the command line. And, remember, this all works fine from the command line.
Not to mention Python, Perl, Lua, and even the lowly Awk and Bourne shell, Not to mention Python, Perl, Lua, and even the lowly Awk and Bourne shell,
have no trouble finding their input file when run as a CGI with the shebang (#! /path/to/binary) have no trouble finding their input file when run as a CGI with the shebang (`#! /path/to/binary`)
as the first line. as the first line.
What actually fixed it What actually fixed it
@ -133,7 +133,7 @@ Why does PHP do this?
I have skimmed [the URL that they asked me to](http://us3.php.net/manual/en/security.cgi-bin.attacks.php). I have skimmed [the URL that they asked me to](http://us3.php.net/manual/en/security.cgi-bin.attacks.php).
They list two points: They list two points:
1. "Interpreters open and execute the file specified as the first argument on the command line." This is true, it's how shebangs work (a file "script.sh" beginning with "#!/bin/sh" is magically transformed to ["/bin/sh", "script.sh"]). It's how Python and Perl launch. I don't get the exploit path here, unless there's some horrible way to misconfigure Apache to do the wrong thing with scripts. 1. "Interpreters open and execute the file specified as the first argument on the command line." This is true, it's how shebangs work (a file `script.sh` beginning with `#!/bin/sh` is magically transformed to `["/bin/sh", "script.sh"]`). It's how Python and Perl launch. I don't get the exploit path here, unless there's some horrible way to misconfigure Apache to do the wrong thing with scripts.
2. If you put the php interpreter under your web server's document root (where files are served from), and then use it to load up php scripts using the `PATH_INFO` environment variable *which is specified by the end user*, then PHP will dutifully serve up every document on your machine. 2. If you put the php interpreter under your web server's document root (where files are served from), and then use it to load up php scripts using the `PATH_INFO` environment variable *which is specified by the end user*, then PHP will dutifully serve up every document on your machine.