|
BugTraq
Re: Re: PHP security (or the lack thereof) Jun 21 2006 11:52PM nabiy hotmail com (2 replies) Re: PHP security (or the lack thereof) Jun 24 2006 05:07AM Ronald Chmara (ron Opus1 COM) (1 replies) RE: PHP security (or the lack thereof) Jun 26 2006 04:06PM Geo. (geoincidents nls net) (3 replies) Re: PHP security (or the lack thereof) Jun 26 2006 05:45PM Paul Schmehl (pauls utdallas edu) (1 replies) Re: PHP security (or the lack thereof) Jun 26 2006 05:32PM Matthias Kestenholz (lists spinlock ch) (1 replies) RE: PHP security (or the lack thereof) Jun 27 2006 11:41AM Geo. (geoincidents nls net) (1 replies) Securing PHP or finding PHP alternatives (was: PHP security (orthe lack thereof)) Jul 08 2006 02:48AM Gezim Hoxha (gezimetc shaw ca) (4 replies) Re: Securing PHP or finding PHP alternatives Jul 11 2006 06:21AM Michael Shigorin (mike osdn org ua) Re: Securing PHP or finding PHP alternatives (was: PHP security (or the lack thereof)) Jul 10 2006 08:37PM Meet Myself on the Internet (me arteabstracta net) Re: Securing PHP or finding PHP alternatives (was: PHP security (orthe lack thereof)) Jul 10 2006 07:25PM Matthias Kestenholz (lists spinlock ch) Re: Securing PHP or finding PHP alternatives Jul 10 2006 05:37PM Crispin Cowan (crispin novell com) (2 replies) Re: Securing PHP or finding PHP alternatives Jul 11 2006 02:50PM Sheryl Coppenger (gubydala his com) (2 replies) Re: Securing PHP or finding PHP alternatives Jul 18 2006 09:35PM Michael Cordover (michael cordover gmail com) Re: Securing PHP or finding PHP alternatives Jul 11 2006 07:54AM SkyFlash (webmaster hackquest de) (1 replies) Re: PHP security (or the lack thereof) Jun 23 2006 08:16PM Crispin Cowan (crispin novell com) (3 replies) Re: PHP security (or the lack thereof) Jun 24 2006 12:43PM Glynn Clements (glynn gclements plus com) Re: PHP security (or the lack thereof) Jun 24 2006 08:28AM Daniel Hulme (bugtraq doublezero uklinux net) |
|
Privacy Statement |
PHP has been introduced as a tool for the web developer. As a language its goal is "to allow web developers to write dynamically generated pages quickly." ( http://www.php.net/manual/en/faq.general.php ). The focus then is to enable the web developer by giving him the tools he needs to create dynamic content, with as little hassle as possible. The web developer need only read a short tutorial ( http://www.php.net/manual/en/tutorial.php ) and he is ready to read, understand and implement the ideas presented in the various example scripts on PHP.net. Unfortunately this situation leaves the web developer uninformed and unprepared to face the hostile environment that is the net.
the only real solution is to change the way the language is presented to new developers. It must be presented in a manner that increases the awareness of the developer so that he able to deploy his application in a safe manner. This means that security needs to be taught from the beginning rather than as a footnote, especially on sites where authoritative teaching is given ( such as PHP.net ). - nabiy
[ reply ]