Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Vendor Build Version field needed, visible in phpinfo()

Aberta
  • Algo errado?
#24,627 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
49/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
c, php
Domínio
backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

Linguagem predominante
C
Estrelas
40.7k
Forks
8.3k
Merge médio
2d 16h
PRs com merge (30d)
151

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de php/php-src

Todas as issues de php/php-src

Issues semelhantes

Mais issues de C

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.