Hi Pierre On 1/11/22 4:48 AM, Pierre Joye wrote:
Also sensitive data goes way beyond arguments, GDPR brings a lot of issues here too. Userland packages like monolog provide filters or custom output, I think that is where it should be handled.
I believe that the author of a function is in the best position to decide whether a specific argument generally holds sensitive data or not. This avoids every exception handler / logger / … having to check what function parameters hold sensitive data and scrubbing them, possibly missing some.
Of course these exception handlers / loggers will still need to take care of any other data they are getting from the request context. But in that case the affected values (e.g. the user object) often need to be explicitly passed into the handler, because they are application specific.
As a side note, the RFC mentions that zend.exception_ignore_args may not be configurable on some shared hosters, it is INI_ALL, so even in the code could change it, any time, back and forth:
I've seen all kinds of broken configurations / broken builds at shared web hosting over time, where things that generally work, do not for some reason.
But good point indeed, I've removed that list item and only left the other one.
Best regards Tim Düsterhus Developer WoltLab GmbH -- WoltLab GmbH Nedlitzer Str. 27B 14469 Potsdam Tel.: +49 331 96784338 duester...@woltlab.com www.woltlab.com Managing director: Marcel Werk AG Potsdam HRB 26795 P -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php
