Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Vendor Build Version field needed, visible in phpinfo()

Aperta
  • Qualcosa non va?
#24,627 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
49/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c, php
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

Lingua principale
C
Stelle
40.7k
Fork
8.3k
Merge medio
2g 17h
PR unite (30g)
159

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di php/php-src

Tutte le issue di php/php-src

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.