Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:116872
MIME-Version: 1.0
References: <ded42b3e-3149-1192-0f86-07715fcb7a3e@woltlab.com>
 <CANS-=pfqDBtfOtbfFWHzB_8eStBWQN5vTDGFe=ehG8B6j3axyw@mail.gmail.com> <70323155-337c-08c1-47c1-1d11fa6e86f8@woltlab.com>
In-Reply-To: <70323155-337c-08c1-47c1-1d11fa6e86f8@woltlab.com>
Date: Wed, 12 Jan 2022 09:30:13 +0100
Message-ID: <CANS-=pe01is8HMm-FZVJdTGPq7X_jZnn6dJ-yEO1=+tOUwy5BQ@mail.gmail.com>
To: =?UTF-8?Q?Tim_D=C3=BCsterhus=2C_WoltLab_GmbH?= <duesterhus@woltlab.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000006e42a805d55e6266"
Subject: Re: [PHP-DEV] RFC [Discussion]: Redacting parameters in back traces
From: kjarli@gmail.com (Lynn)

--0000000000006e42a805d55e6266
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 12, 2022 at 9:17 AM Tim D=C3=BCsterhus, 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 value=
s
> > 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.

--0000000000006e42a805d55e6266--