WordPress.org

Make WordPress Core

Opened 14 months ago

Closed 7 months ago

Last modified 5 months ago

#47343 closed defect (bug) (invalid)

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

Reported by: laserjobs Owned by:
Milestone: Priority: normal
Severity: normal Version: 5.2.1
Component: Upgrade/Install Keywords:
Focuses: Cc:

Description

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

Change History (6)

#1 @SergeyBiryukov
14 months ago

  • Component changed from General to Upgrade/Install

#3 @garrett-eclipse
7 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

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.

#4 @garrett-eclipse
7 months ago

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

#5 @SergeyBiryukov
7 months ago

#49004 was marked as a duplicate.

Note: See TracTickets for help on using tickets.