Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:116853 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 76137 invoked from network); 10 Jan 2022 12:57:03 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 Jan 2022 12:57:03 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 7D749180545 for ; Mon, 10 Jan 2022 06:05:46 -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,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-203.mailbox.org (mout-b-203.mailbox.org [195.10.208.52]) (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, 10 Jan 2022 06:05:45 -0800 (PST) Received: from smtp1.mailbox.org (smtp1.mailbox.org [80.241.60.240]) (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-203.mailbox.org (Postfix) with ESMTPS id 4JXbFd2rF5zQjmY for ; Mon, 10 Jan 2022 15:05:41 +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=1641823539; 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; bh=jHmuLF6mKqMl+ZbtvMvLXHK1COQDYMTX2ZXmkqaIL9E=; b=y/UVxkuktyM6rXIR7Qm6dgpujDgiWcNqY0HK6eyGRPCrY9koYlKoZYORitJ2rbFwRNJIXo vV8OSSCyuLSwHKFNRcExWIfOUX3XsJC0JsDUCx8r6z9WZBOZj/ncI9a25ruq5C7g1Wspop q2wErzG5WIv9V3me8Y5IzxyL+xBSgUNBZRrd8FJoeCfJm/lWo4NNL5SO14gL15zvQKsNuL N3iLB/UVg71Sevhq/piIZMH9BikdGVSTrgVpS6vcGXqAytKoEzeQGWbTqWUEvjsJuUd3tA vs6dGbZ57GNQLBg1Rv+jzX1ze5krEH//qO22HI8dPW+8+v3nzkDUWr82jL/MLg== To: PHP internals Message-ID: Date: Mon, 10 Jan 2022 15:05:36 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: RFC [Discussion]: Redacting parameters in back traces From: duesterhus@woltlab.com (=?UTF-8?Q?Tim_D=c3=bcsterhus=2c_WoltLab_GmbH?=) Hi Internals! this is a follow-up for my "Pre-RFC" email from last Friday, January, 7th. Christoph Becker granted me RFC editing permissions and I've now written up our proposal as a proper RFC: https://wiki.php.net/rfc/redact_parameters_in_back_traces I recommend also taking a look at my previous email: https://externals.io/message/116847 It contains some additional context that did not really fit within the language of a "neutral" RFC that will remain as the permanent record. - 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. - 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. 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