Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:61258
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.170 as permitted sender)
Message-ID: <50033454.6080100@gmail.com>
Date: Sun, 15 Jul 2012 23:21:24 +0200
User-Agent: Thunderbird
MIME-Version: 1.0
To: internals <internals@lists.php.net>
References: <CAAyV7nFRT24rksh6iDWxstfQwJ4+KdEC7Zs6EC8wBtJ8Zorf7w@mail.gmail.com> <CAKZjf5ROuK-Kt1GAPJm0A2-mksw2kJ7C4bOMtz1+dPrYheqzSA@mail.gmail.com> <CAAyV7nFBk1j20LiYvz--2K+BPNgm6_WEGPtY0t5oC57PhCupVg@mail.gmail.com> <4FFFF84D.9070202@rotorised.com> <5000990F.30105@gmail.com> <CAKZjf5SLGV92xrynnHdBRexczOhryuJBQVyZpbKsTnQ1iPx94g@mail.gmail.com> <CAN+gjSfuhkupfhV-fvZBMHTF8JQ_HF7KhOkj6j1we14mL1HCog@mail.gmail.com> <CAKZjf5Tj_3c7T9zZBv8Tztvqa5zeJRAHHe7_HQNpCijsUz-qtA@mail.gmail.com> <CAKZjf5Sf7FBqMwQwuoyLm6OEQLO3wBf0yHoVCCHE2envwqdSQQ@mail.gmail.com>
In-Reply-To: <CAKZjf5Sf7FBqMwQwuoyLm6OEQLO3wBf0yHoVCCHE2envwqdSQQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [PROPOSED] password_hash RFC - Implementing simplified
 password hashing functions
From: keisial@gmail.com (=?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?=)

On 15/07/12 22:07, Alex Aulbach wrote:
> 2012/7/14 Andrew Faulds <ajfweb@googlemail.com>:
>> Well... if people have poorly configured servers spitting out debug
>> info in production mode, I don't think it is our problem. It is
>> theirs.
> Do you want to make it secure or do you want to discuss?
Seems Andrew mail didn't get to the list.
Yes, production servers shouldn't be showing debug info. But we know
that a large fraction of them do.
As coder of a php application, I often can't set the configuration of
the system
where it will be installed. Sometimes not even the person installing it
can set
it correctly (eg. shared hostings), it can be changed under your foot
(eg. an update,
someone did so to debug a different application...) or even be set
explicitely (I
want my users to warn me when they see errors !).
If spitting out errors prevented XHTML validation, I wouldn't care that
much (obviously,
the code shouldn't generate the warning to begin with, but it's not a
big deal if users
were briefly shown it). But we are talking about passwords and password
hashes. Not
something you want to risk exposing. Specially when we are trying to
make a good
interface to encourage secure handling of passwords.


PS: Alex, your non-displayable exception would indeed work (although I
would make it
a class property).