Message during update : authenticity could not be verified as no signature was found

[laserjobs]

During the update to 5.2.1 got the following message in the control panel:
"The authenticity of wordpress-5.2.1-no-content.zip could not be verified as no signature was found."

The update was sucessful

[desrosj]

Related: #45806, #39309.

[garrett-eclipse]

This message can be safely ignored. In WP 5.2 the package signature code was being implemented but needed to be rolled back due to some PHP incompatibilities. The messaging was left and can be ignored for now. In future the signature verification will be re-implemented.

[garrett-eclipse]

More definitive information on this;

Signature verification is not yet enabled, so this message is expected to be displayed.
[44954] introduced experimental package signature verification. However, there were some difficult problems identified that need to be solved in order to securely use this feature in practice. You can read more about this here ​https://make.wordpress.org/core/2019/08/16/ssl-for-auto-updates/.

Reference - https://core.trac.wordpress.org/ticket/49004#comment:4

[SergeyBiryukov]

#49004 was marked as a duplicate.

[felipeloureirosantos]

Also reported on Brazilian forums: ​https://br.wordpress.org/support/topic/problema-na-atualizacao-do-wordpress-2/

[SergeyBiryukov]

Duplicate of #47315.