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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <877k5866ko.fsf@deneb.enyo.de>
From: fw at deneb.enyo.de (Florian Weimer)
Subject: AW: 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*.