On Wed, April 11, 2012 5:14 pm, Yasuo Ohgaki wrote:
> I think my RFC confused people on this list due to improper
> descriptions
> and too much information. Sorry for the confusion. I revised the RFC
> so
> that most important points can be understood at a glance.
>
> https://wiki.php.net/rfc/nophptags
We all know there are a LOT of bad scripts out there.
A *LOT* of bad scripts.
With major security holes in them.
I do not see your average PHP scripter changing that behavior: It's
just so easy to write a PHP script, which is why it's so popular.
Now, you are going to open up all the inexperienced scripters to code
exposure when they start using this cool new feature of being lazy and
not typing that silly <?php tag.
And that code being exposed will have major security holes in it.
This is just not a good idea...
Instead of random bots attacking random URLs hoping to hit pay dirt
for an SQL injection, you will have bots that:
Use google to find stuff that looks like raw PHP code.
Scape page to look for mysql.*$_POST
Attack site.
Unless I'm really missing something here, you put a few million
people's code at risk, for a feature that has dubious value in the
first place.
--
brain cancer update:
http://richardlynch.blogspot.com/search/label/brain%20tumor
Donate:
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
