full-disclosure - AW: securing php

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

From: rgerhards at hq.adiscon.com (Rainer Gerhards)
Subject: AW: securing php

But it is still another hurdle ;) Remeber, security is the art of moving
as many hurdles in the way as possible. Hopefully the attacker is
exhausted before he reaches the last one. And, yes, I agree it is good
to be always reminded that some of the hurdles are small ;)

Rainer

> -----Original Message-----
> From: Florian Weimer [mailto:fw@...eb.enyo.de] 
> Sent: Wednesday, August 20, 2003 11:07 AM
> To: vogt@...senet.com
> Cc: zorkshin@...pabay.rr.com; full-disclosure@...ts.netsys.com
> Subject: Re: AW: [Full-Disclosure] securing php
> 
> 
> vogt@...senet.com writes:
> 
> > You an enable PHP's "Safe Mode", which goes a long way to
> > closing these holes, but it's not a 100% solution.
> 
> PHP uses many libraries which were not designed to cope with malicious
> input from the application.  That's why PHP Safe Mode is unsafe *by*
> *design*.
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>