Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:125644 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id D3D011A00BD for ; Fri, 20 Sep 2024 17:28:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1726853460; bh=zYj8sR/s/O3BihATIUcRcAsD7IFa4BNO3a4j+sBZ0ww=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=nKRd8DuuseVr+6ZXPmtTGuLTvJS7m6SCZOx2h8PPNZQwRnebNVKuSX5Tcq5mN8G/J fIEVUkjGhnL1cgyUNi+1SmNH/Om/R0eLani13RPNPecpz5GxJDPEdLUAUpXQ7DUfqk 1Qpzh1V5zXBJnSrOUW/vBlvsHbLTvfv+TOfymY/Hu02fdNsvE3pP68R7I2MiDXR+Ch KWz3NHJRxANc+Y/YB+i46Yoh77EUFmquefkNx9nTW54MbvUHq2ccNNdMpeaBkJ3vry VUUlz/tPdCcua+hvNczoH8twKpDeefmBMbxa9HMzz684q/KItLUneeyrKMefJxGrhb 4/6Kgcyt3xUSg== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 3FFC1180053 for ; Fri, 20 Sep 2024 17:30:59 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,HTML_MESSAGE, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: No X-Envelope-From: Received: from mx1.dfw.automattic.com (mx1.dfw.automattic.com [192.0.84.151]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 20 Sep 2024 17:30:58 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mx1.dfw.automattic.com (Postfix) with ESMTP id 982A6341021 for ; Fri, 20 Sep 2024 17:28:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=automattic.com; h=content-type:content-type:x-mailer:mime-version:references :in-reply-to:message-id:subject:subject:from:from:date:date :received:received:received:received:received:received; s= automattic1; t=1726853329; bh=zYj8sR/s/O3BihATIUcRcAsD7IFa4BNO3a 4j+sBZ0ww=; b=bQdpNs3yx+6tqZn8+z+bSJVCFEkq+06p2SjIX03e32mIwdL3mp 0lOxNKEXepWKLXgIagMbyNunodlv4cpalPFs1kmYR6rgQv50Y9aFIxNkDZ4KekZB KuEjFi+ySFRuRoox/cZjXKFGxhamvUvgQBUIEmz9yJ6xQ/tnHHjYS1PB8Vj3KC3c UGHl173busBylGmyPVeYnFhdhIprV2tu2oSvNm3Uvv3nn0LT0gcCVOyaej86OYDw ypmvg2SMY3f2MbOuDmalXwbb5LQOdHWN9qEDFV0i6SItjFTHQKSwgL7CoSwpbz8t ztuyl+2k52rhl3h57j0NAI8lA8OMJBVuBaHA== X-Virus-Scanned: Debian amavisd-new at wordpress.com Received: from mx1.dfw.automattic.com ([127.0.0.1]) by localhost (mx1.dfw.automattic.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lR7J4mD2RBvB for ; Fri, 20 Sep 2024 17:28:49 +0000 (UTC) Received: from smtp-gw.dca.automattic.com (smtp-gw.dca.automattic.com [192.0.97.210]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.dfw.automattic.com (Postfix) with ESMTPS id 90B51340FFD for ; Fri, 20 Sep 2024 17:28:49 +0000 (UTC) Authentication-Results: mail.automattic.com; dkim=pass (2048-bit key; unprotected) header.d=automattic.com header.i=@automattic.com header.b="Ot0/28u2"; dkim=pass (2048-bit key; unprotected) header.d=automattic.com header.i=@automattic.com header.b="fRAXU+lf"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=automattic.com header.i=@automattic.com header.b="LwLzl2Ws"; dkim-atps=neutral Received: from smtp-gw.dca.automattic.com (localhost.localdomain [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-gw.dca.automattic.com (Postfix) with ESMTPS id 33B51A0984 for ; Fri, 20 Sep 2024 17:28:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=automattic.com; s=automattic2; t=1726853329; bh=zYj8sR/s/O3BihATIUcRcAsD7IFa4BNO3a4j+sBZ0ww=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Ot0/28u2uV8UizEeS/cThKeimUP+FJV2ZKN0YMNF9frjTwthfl8Lah4IxhGoQ3U2Q Adqx3zOeo3b9bVuXeDJgieTRIZXvHj8uMQ5xoKWyxHjwVVXYkqlxtI0IitcGxeClFY r2075pgU4e27Wc9BOiT4nJbD5BavA/ec/iB9bhJuOnrofIGqZaV1Ok1IfyTPHffjWD Z/GALQyLKK8KsG5C3LvvlA3P6qlag+n5XeeDhXvBxOVRt1J0Y3MLcIcuOW7B2lleA7 iISvWAPE/MRzYmy54E+GMny5MHIcjv0kQt2TxaWfqZRL4HONQCo0nmx0G5sbbtHEuZ 3dydRHJXeeS5A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=automattic.com; s=automattic1; t=1726853329; bh=zYj8sR/s/O3BihATIUcRcAsD7IFa4BNO3a4j+sBZ0ww=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=fRAXU+lfhoVGHAaz5P2itdlUtrNuSe/4SlwydbLkxfLw1Bf7DHeyxGd1QXaCgyjyc FYgWrGBre74PlVsKjeLHzy6uV7OXWclulapQ336CEXJW6jkW2hJ8AHNsy/3bM+vIkQ N/Fvss5kY8r2IERP5sTHb4YUo4tGVojLbGdTVouGnzIU2yj0I8aK57za3DfxKTLRnB 3A2FuO3uSYuFAwb0ScDuxwQOeQ3EwCJyXLWA/C5Y3GgQU3VxXIZIiBDpmHvr3fjOFg hmzp88gjOGj4XS8ErjHL8C+9YH3lbabS9WPiqhK86HdLuDSRtVIBSxksFKJrNg2W5p J13oua4QN1fGw== Received: from mail-pg1-f198.google.com (mail-pg1-f198.google.com [209.85.215.198]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-gw.dca.automattic.com (Postfix) with ESMTPS id 0A341A09BA for ; Fri, 20 Sep 2024 17:28:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=automattic.com; s=automattic2; t=1726853329; bh=zYj8sR/s/O3BihATIUcRcAsD7IFa4BNO3a4j+sBZ0ww=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=LwLzl2Ws78qUeUW9D8xlQ8gUdQYU0ofS482hlcXwSspk48RLxLwVzI9Tvyh2dpN7q pDAYFGbtIMvjwaT1qm2Mh/3VxorujJ5qMcgTS9NNidZy/u+CrrprSDDJKMNi0e/vqf wmyS/NBmiK4j/32HT+KXUm0nnMR+FRnLU3C8E296PBLzjBFm7sBCZTC9aVcjjYCgSE moxndmDAa8f3FESwrq6UgzNbdDdCUWsjlq0UOqJFybBGUgeYd+/Nrr0nU68oV7tpYh 3EtB6zw/9S8PmNneTXF5tTL42Txbho0Rxe40bEzFm61NyVfBiDP+nHm2lG+06QKdFc MkVYWY7m/ddOQ== Received: by mail-pg1-f198.google.com with SMTP id 41be03b00d2f7-7d904fe9731so2018510a12.3 for ; Fri, 20 Sep 2024 10:28:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726853328; x=1727458128; h=mime-version:references:in-reply-to:message-id:subject:cc:to:from :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Fgv3TnMaLDXIuo1+8zTzGhUcUfybsvE+kQQVuZ5d0ck=; b=qb+Qs6Kzs96AA4fvFQu5NAweCeWVriM3JDUPAFW/4WZWpKnnFe/kngQ802ctvPN1nR /sQMcl21EKOBfkLTztnGGbKeuVSNaEOZ8EZQFlyEKP6U0th+4jBeN+A55pyf+vtQDTZT pzb2gPqVxPxU+PTOrbgPEzAI4fjuxp4CXNejldIJVIf69P4B3u/iBbcgXeMlwde6JY7s sAQFH3vXiflB07tPQRRw7fjKVl7WSOUaFi6qjzzdflVAskTWg9VSMxzF1pMXrAHZ8eo/ m+FMC1DvlcNK3sHwv7uMuw1f4ptG5L5hHz+v5e2+q+78UBEIIovYn5FGI7FIHR9/W5+z 483Q== X-Forwarded-Encrypted: i=1; AJvYcCU66IlBhqioG0yGVeODDKXyhX/YdEJ+iQB8o1R5yYWxoR97a2i44kZLKkACIkUfEtIpSdIwE86eR+Y=@lists.php.net X-Gm-Message-State: AOJu0YyZkXAjUoIPE3ts2QctnGhUYVBE+QSP9KONNy/v4MlivmPSJweC ZjnULSA70zYd11c3hOq/CDQEs/UxifiUCnh17l2xM0q8Rg0K+mmT6e4yNOpC9SKh6LA45cClP9V W8xYu518qNjM1ZKZCZw5Jfry8xyyCpUm/FhVwA0aUiAzQjBJ19nkdkfs= X-Received: by 2002:a05:6a20:6f08:b0:1cf:3a52:6ad6 with SMTP id adf61e73a8af0-1d30a96d7aamr5540963637.24.1726853327668; Fri, 20 Sep 2024 10:28:47 -0700 (PDT) X-Google-Smtp-Source: AGHT+IFpzubNJmZd0vwPlR469Z4fKyhnJehniMdjzsEB/qwY1IJJbqS+ZRJCrRKwGD9qexcfYbykaw== X-Received: by 2002:a05:6a20:6f08:b0:1cf:3a52:6ad6 with SMTP id adf61e73a8af0-1d30a96d7aamr5540931637.24.1726853327116; Fri, 20 Sep 2024 10:28:47 -0700 (PDT) Received: from [10.131.13.50] ([67.23.203.32]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-71944ab5115sm10067772b3a.55.2024.09.20.10.28.46 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Sep 2024 10:28:46 -0700 (PDT) Date: Fri, 20 Sep 2024 10:28:46 -0700 (PDT) X-Google-Original-Date: 20 Sep 2024 10:28:45 -0700 X-Google-Original-From: Dennis Snell To: Arvids Godjuks Cc: Hammed Ajao , Rob Landers , Adam Zielinski , Mike Schinkel , PHP internals Subject: Re: [PHP-DEV] Zephir, and other tangents Message-ID: In-Reply-To: References: <8D420123-4ECF-48FD-A9C3-F80C60457A37@newclarity.net> <7EA884D2-0F37-4BF1-AC97-DB6953C944E6@automattic.com> Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net x-ms-reactions: disallow MIME-Version: 1.0 X-Mailer: Unibox (443:23.6.0) Content-Type: multipart/alternative; boundary="=_0B071799-C3F1-4546-8D92-D314F3E03523" From: dennis.snell@automattic.com (Dennis Snell) --=_0B071799-C3F1-4546-8D92-D314F3E03523 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable > On Sep 20, 2024, at 12:56 AM, Arvids Godjuks w= rote: >=20 >=20 > On Fri, 20 Sept 2024 at 09:17, Dennis Snell > wrote: >=20 >>=20 >> Hi Hammed, thank you for taking the time to read through this and share = your thoughts. >>=20 >>=20 >>> snip >>>=20 >>=20 >>>=20 >>> Cheers, >>> Hammed >>>=20 >>>=20 >>>=20 >>=20 >> Hope you have a nice weekend. Cheers. >>=20 >>=20 >>=20 >=20 >=20 > Hello everyone, >=20 > I want to chip in here, since reading the thread lead me into a state of = cognitive dissonance. >=20 Hi=C2=A0Arv=C4=ABds, that sounds stressful. This is definitely a wavering t= hread, as noted by the =E2=80=9Ctangents=E2=80=9D subject. As far as the em= ail you=E2=80=99re replying to, the main point is that if PHP offered a way= to embed safe native-like extensions in a sandbox, then lots of the pressu= re to add and maintain extensions would drop from the host and provider and= enable the customers to manage that on their own, and open many doors for = PHP. A WASM runtime engine inside PHP would be a viable path to get to that= point. > I've been in PHP world for a long=C2=A0time, about 3 years shy of how old= Wordpress is. When I'm reading "shared hosting" and "WASM" and knowing how= managed hosting works, I have to ask: What type of la-la land is this conv= ersation is taking place in? > All managed wordpess hosting is locked down hard. Extensions are very lim= ited and everything that allows any type of freedom is disabled, functions = are disabled en mass. I have to ask: knowing the history of past 27 years, = what managed hoster in their right mind and sanity will allow WASM to be en= abled=C2=A0to bypass ____A L L _____ PHP security features and allow PHP co= de do anything it wants? On a shared hosting... I seriously want to know an= swer to this question, because I firmly believe there was zero risk and sec= urity assessment not only done, but it hasn't been even a twinkle in the ey= e. >=20 These are good questions. The basic point of confusion might stem from what= the security domain is for a WASM runtime. It=E2=80=99s actually precisely= because of the concerns you raise that WASM is a candidate here, being san= dboxed by default and unable to interact with the host system. That is, a WASM extension not only can=E2=80=99t bypass any PHP security fe= atures, but it=E2=80=99s significantly more constrained than any PHP code i= s. Managed hosts are locked down largely because of the security concerns t= hat are categorically not present with the system we=E2=80=99re discussing,= so being able to offer more on their platforms without having to dedicate = additional resources to it could be a nice selling point. >=20 >=20 > On VPS/Decicated you can run whatever you want, so you don't have the lim= itations. >=20 I mentioned this in my email; I appreciate that many folks around here have= full control over their infrastructure, but when building platform like Wo= rdPress or any of the other PHP frameworks, we just don=E2=80=99t have the = liberty of having that control. In any case, even some very large shops who= write and manage their own PHP extensions are constantly on the hook for s= ecurity issues and updates and breakages. I=E2=80=99m sure we=E2=80=99d do = much more at Automattic to extend PHP if we could do so without the securit= y, platform-dependancy, and build issues involved in maintaining custom ext= ensions. >=20 >=20 > On other note - people have pointed out how big body of work it is. If yo= u want to sponsor WASM development for PHP, I suggest Automatic open their = wallet and put in 2-3 million $ a year for the next 5-10 years to PHPFounda= tion and find devs who are capable and willing to do this job. Honestly, I = think you might find people to want to do that rather than lack of money be= ing the cause of it. >=20 I=E2=80=99m not sure why you=E2=80=99re singling out Automattic, since nobo= dy from Automattic started this thread or requested other people provide un= funded volunteer work, or why you=E2=80=99re expecting a single corporate e= ntity to fully fund long-term planned features in the language. Is that how= PHP normally grows? I=E2=80=99m not familiar with the process. My goal in sharing here is to help better represent my own perspective of W= ordPress=E2=80=99 needs based on what I=E2=80=99ve seen. It=E2=80=99s long = been on my list to propose a WASM RFC, but because I personally haven= =E2=80=99t had the priority available to get an implementation working I ha= ven=E2=80=99t done so. It=E2=80=99s my impression from the documentation th= at the purpose of these email threads w.r.t. RFCs is to gather interest and= input before any RFC would be put together, to hold these discussions befo= re anyone commits any major time to it. >=20 >=20 > --=C2=A0 >=20 >=20 > Arv=C4=ABds Godjuks+371 26 851 664 > arvids.godjuks@gmail.com >=20 > Telegram: @psihius=C2=A0https://t.me/psihius >=20 >=20 >=20 >=20 >=20 Warmly, Dennis Snell --=_0B071799-C3F1-4546-8D92-D314F3E03523 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable

On Sep 20, 2024, at 12:56 AM, Arvids Godjuks <arvids.godjuks@gmail.= com> wrote:

On Fri, 20 Sept 2024 at 09:17, Dennis Snell <dennis.snell@automattic.com> wrote:
Hi Hammed, thank you for taking the time to read through this and shar= e your thoughts.

snip


Cheers,
Hammed

Hope you have a nice weekend. Cheers.

Hello everyone,

I want to= chip in here, since reading the thread lead me into a state of cognitive d= issonance.

Hi=C2=A0Arv=C4=ABds, that sounds stressful. This is definitely a waver= ing thread, as noted by the =E2=80=9Ctangents=E2=80=9D subject. As far as t= he email you=E2=80=99re replying to, the main point is that if PHP offered = a way to embed safe native-like extensions in a sandbox, then lots of the p= ressure to add and maintain extensions would drop from the host and provide= r and enable the customers to manage that on their own, and open many doors= for PHP. A WASM runtime engine inside PHP would be a viable path to get to= that point.

I've been= in PHP world for a long=C2=A0time, about 3 years shy of how old Wordpress = is. When I'm reading "shared hosting" and "WASM" and knowing how managed ho= sting works, I have to ask: What type of la-la land is this conversation is= taking place in?
All manag= ed wordpess hosting is locked down hard. Extensions are very limited and ev= erything that allows any type of freedom is disabled, functions are disable= d en mass. I have to ask: knowing the history of past 27 years, what manage= d hoster in their right mind and sanity will allow WASM to be enabled=C2=A0= to bypass ____A L L _____ PHP security features and allow PHP code do anyth= ing it wants? On a shared hosting... I seriously want to know answer to thi= s question, because I firmly believe there was zero risk and security asses= sment not only done, but it hasn't been even a twinkle in the eye.

These are good questions. The basic point of confusion might stem from= what the security domain is for a WASM runtime. It=E2=80=99s actually prec= isely because of the concerns you raise that WASM is a candidate here, bein= g sandboxed by default and unable to interact with the host system.

That is, a WASM extension not only can=E2=80=99t bypass any PHP securi= ty features, but it=E2=80=99s significantly more constrained than any PHP c= ode is. Managed hosts are locked down largely because of the security conce= rns that are categorically not present with the system we=E2=80=99re discus= sing, so being able to offer more on their platforms without having to dedi= cate additional resources to it could be a nice selling point.


On VPS/De= cicated you can run whatever you want, so you don't have the limitations.

I mentioned this in my email; I appreciate that many folks around here= have full control over their infrastructure, but when building platform li= ke WordPress or any of the other PHP frameworks, we just don=E2=80=99t have= the liberty of having that control. In any case, even some very large shop= s who write and manage their own PHP extensions are constantly on the hook = for security issues and updates and breakages. I=E2=80=99m sure we=E2=80=99= d do much more at Automattic to extend PHP if we could do so without the se= curity, platform-dependancy, and build issues involved in maintaining custo= m extensions.


On other = note - people have pointed out how big body of work it is. If you want to s= ponsor WASM development for PHP, I suggest Automatic open their wallet and = put in 2-3 million $ a year for the next 5-10 years to PHPFoundation and fi= nd devs who are capable and willing to do this job. Honestly, I think you m= ight find people to want to do that rather than lack of money being the cau= se of it.

I=E2=80=99m not sure why you=E2=80=99re singling out Automattic, since= nobody from Automattic started this thread or requested other people provi= de unfunded volunteer work, or why you=E2=80=99re expecting a single corpor= ate entity to fully fund long-term planned features in the language. Is tha= t how PHP normally grows? I=E2=80=99m not familiar with the process.

My goal in sharing here is to help better represent my own perspective= of WordPress=E2=80=99 needs based on what I=E2=80=99ve seen. It=E2=80=99s = long been on my list to propose a WASM RFC, but because I personally haven= =E2=80=99t had the priority available to get an implementation working I ha= ven=E2=80=99t done so. It=E2=80=99s my impression from the documentation th= at the purpose of these email threads w.r.t. RFCs is to gather interest and= input before any RFC would be put together, to hold these discussions befo= re anyone commits any major time to it.


--=C2=A0

Arv=C4=ABds Godjuks
+371 26 851 664
Telegram: @psihius=C2=A0https://t.me/psihius

Warmly,
Dennis Snell
--=_0B071799-C3F1-4546-8D92-D314F3E03523--