| |||||||||||||
|
| |||||||||||||
*Another* hole?*Another* hole?Posted Jul 23, 2002 21:39 UTC (Tue) by strombrg (guest, #2178)In reply to: *Another* hole? by gonkgonk Parent article: Scripting flaw threatens Web servers (News.com)
Actually, PHP seems to be fairly security-problem-prone. You have to disable functionality that most PHP code assumes you have, in order to get a subset that doesn't make it too easy to shoot yourself in the foot. So if you plan on code resuse with PHP, don't plan on your code being especially secure.
(Log in to post comments)
*Another* hole? Posted Jul 25, 2002 20:34 UTC (Thu) by JLCdjinn (guest, #1905) [Link] Could you please elaborate (or point me in the direction of a resource) on what functionality needs to be turned off in order to bring more security to PHP? I'm just curious to know about how the portability might be hindered, and plan for it accordingly. Thanks much, John
|
|
||||||||||||