Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116957 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 87149 invoked from network); 31 Jan 2022 08:41:03 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 31 Jan 2022 08:41:03 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 941B4180088 for ; Mon, 31 Jan 2022 01:54:59 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS199118 195.10.208.0/24 X-Spam-Virus: No X-Envelope-From: Received: from mout-b-105.mailbox.org (mout-b-105.mailbox.org [195.10.208.50]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 31 Jan 2022 01:54:58 -0800 (PST) Received: from smtp102.mailbox.org (smtp102.mailbox.org [IPv6:2001:67c:2050:105:465:1:3:0]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-b-105.mailbox.org (Postfix) with ESMTPS id 4JnNhc3R5Sz9sTn for ; Mon, 31 Jan 2022 10:54:56 +0100 (CET) X-Virus-Scanned: amavisd-new at heinlein-support.de DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=woltlab.com; s=MBO0001; t=1643622894; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XDzZbVs/WD+UHrS3mARBZb1w5OJisvyaTeFHiC/em9k=; b=G+1ygRwZ1e9Dykkm9R6PISx1jOfNE5uL5de1HAlny5DsYm9dLC6thNw4wcEtL2oANHtZBg +2GF+QrVHN2rEhbIP8Kh2N3Y5BDTPXdd6GOGpxjtuULbUY2wyCBKwLblZ9pAdlKynQ4EyI de3BTBETsxFtXe0hTTG3cso9YFQcV9JHBukTZXNv7YAFfwwuC5wVCVfOXQFfJlSr430NLt AlfmFZnCoPWWIijfaXJcvLv87kEc6umFWCKnN+aWbmV6vrwhSIR7/WAA5jSbrzB4l03+57 8c/ZxiWpG+ZKua7uwxVsUatvgerpw8qjpkoXI2ddwOjmH4iiazNbE33E84goWQ== Message-ID: <1d272d70-1d78-5bd1-2e11-9f903c755073@woltlab.com> Date: Mon, 31 Jan 2022 10:54:48 +0100 MIME-Version: 1.0 Content-Language: en-US To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] RFC [Discussion]: Redacting parameters in back traces From: duesterhus@woltlab.com (=?UTF-8?Q?Tim_D=c3=bcsterhus=2c_WoltLab_GmbH?=) Hi Internals! On 1/10/22 15:05, Tim Düsterhus, WoltLab GmbH wrote: > https://wiki.php.net/rfc/redact_parameters_in_back_traces At the end of last week I've updated the RFC a little based on the questions Derick Rethan asked me for episode #97 of PHP Internals News podcast: https://phpinternals.news/97 > - As indicated within the RFC and my previous email we still need a more > experienced developer for the final implementation, as I have next to no > experience with PHP's implementation. > > Specifically adding this attribute to existing functions is not clear to > me. It is probably required to update the stub parser/generator to add > support for attributes? If someone creates an example implementation for > one function, I'll likely be able to apply this to other functions myself. I also managed to figure this out. The proof of concept implementation at https://github.com/php/php-src/pull/7921 now adds the \SensitiveParameter attribute to PDO::__construct()'s $password parameter and to password_hash()'s $password parameter. > - The RFC Impact to Opcache is not clear to me. I don't believe there is > any, but I am not sure. So if someone knows, I'm happy to update that > section. For this I got a confirmation in private that Opcache will not be affected. - I believe I've answered all open questions and I also managed to resolve the open issues I listed in my initial email. As more than two weeks have passed since I started this discussion thread and as the discussion appears to have died down by now I'd like to start the vote on this RFC. I plan to open voting on Wednesday, February, 2nd. Voting will run 2 weeks, 2/3 majority with the concept being voted on as explained in the "Proposed Voting Choice" section: https://wiki.php.net/rfc/redact_parameters_in_back_traces#proposed_voting_choices This being my first RFC, please let me know if I missed something with regard to the procedure! Best regards Tim Düsterhus Developer WoltLab GmbH -- WoltLab GmbH Nedlitzer Str. 27B 14469 Potsdam Tel.: +49 331 96784338 duesterhus@woltlab.com www.woltlab.com Managing director: Marcel Werk AG Potsdam HRB 26795 P