Vendor Build Version field needed, visible in phpinfo()
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start by reading the phpinfo() implementation and how the Core section reports version details; the issue does not name source files or tests. Trace where the PHP version and build date are produced, then determine how a vendor-provided build version could be represented alongside them. Done means phpinfo() displays a separate “Vendor Build” item that exposes the vendor’s build version.
由索引模型根據 Issue 內容生成。
描述
Congratulations on the rapid and successful rollout of the PHP2Shell mitigation.
When vendors updated their builds to include the fixes, some did not update the Version stamps to reflect the PHP.net version, which created a lot of confusion. I believe that there were thousands of support calls to hosting providers that could have been avoided if the version stamp reported by phpinfo() was more complete. For example, CloudLinux created a version containing both CVE fixes, which still showed up in phpinfo() as 8.5.11. Their internal version nomenclature was not visible, and everyone had to take their word for it that it contained the fixes. The build date alone did not offer proof that the CVE fixes were applied. A day or two later, they updated the primary version stamp to 8.5.12, and issued a statement explaining the process.
It would be beneficial if an item could be added to the phpinfo() output to display the build version produced by the vendor or hosting provider that updated the code. For example, under the "Core" section, include "Vendor Build" as a separate item. Then, when another update blitz like this one occurs again, users would be able to more easily cross reference the full version number with changelogs or reports issued by their hosting providers. (and not swamp their hosting provider with unneccessary support calls.)
Thanks for considering,
-JDB
- 主要語言
- C
- 星號
- 40.7k
- 分支
- 8.3k
- 平均合併
- 2 天 16 小時
- 30 天內合併 PR
- 151
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
php/php-src 的其他 Issue
-
Bug Status: Needs Triage
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
zend_set_local_var() overwrites existing compiled variable (CV) zval without calling zval_ptr_dtor()未關閉Bug Status: Needs Triage
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
Case-insensitive substr_compare, ksort, krsort are still locale-dependent可能已有人在做 @lazerg 於 3 天前認領。 未關閉Bug Extension: standard Status: Verified
難度 2/5 1-3 小時 新手友好度 73/100
維護者通常 1 天內回覆
-
master: part of the mbstring bailout fix got lost in a merge可能已有人在做 @lazerg 於 4 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 65/100
-
難度 2/5 1-3 小時 新手友好度 76/100
ChefKissInc/Inferno#319 ·
-
llvm-tools
難度 1/5 1 小時以內 新手友好度 72/100
llvm/llvm-project#235522 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
-
priority:medium type:chore
難度 1/5 1-3 小時 新手友好度 84/100
crazy-goat/php-fpm-ng#1041 ·
維護者通常 1 天內回覆