Re: RFC [Discussion]: Redacting parameters in back traces
| From: | Lynn | Date: | Wed, 12 Jan 2022 08:30:13 +0000 |
| Subject: | Re: RFC [Discussion]: Redacting parameters in back traces | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-116872@lists.php.net to get a copy of this message | ||
On Wed, Jan 12, 2022 at 9:17 AM Tim Düsterhus, WoltLab GmbH <
duesterhus@woltlab.com> wrote:
> Hi Lynn
>
> On 1/11/22 11:23 AM, Lynn wrote:
> > One possible addition; would it be possible to analyze the masked values
> > and mask any 100% matches elsewhere?
>
> No, this is not in scope for this RFC, as it would require accurate
> tracking of variable contents across reassignments and possibly function
> calls.
>
> My understanding is that this basically would require support for
> tainted variables, i.e. this very old RFC:
> https://wiki.php.net/rfc/taint
I was thinking more of a "keep track of the values replaced, and in the
end purge all those values from the end-result" kinda thing.