![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 6 years ago
Closed 6 years ago
#51428 closed defect (bug) (duplicate)
"The authenticity could not be verified as no signature was found"
| Reported by: | rgentle | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Security | Version: | 5.5.1 |
| Severity: | normal | Keywords: | |
| Cc: | Focuses: |
Description
I have received this message on a number of my websites when trying to manually update to the latest WP:
The authenticity of wordpress-5.5.1.zip could not be verified as no signature was found
I have seen forums saying WP team are doing something about this, but that was over 6 weeks ago.
Attachments (1)
Change History (3)
#1
@
6 years ago
- Component General → Security
Related support forum response:
https://wordpress.org/support/topic/the-authenticity-of-wordpress-5-5-no-content-zip-could-not-be-verified/#post-13243577
#2
@
6 years ago
- Milestone Awaiting Review
- Resolution → duplicate
- Status new → closed
- Summary Problems updating WP 5.5.1 on several sites → "The authenticity could not be verified as no signature was found"
Hi there, welcome to WordPress Trac!
Thanks for the report, we're already tracking this issue in #47315.
Note:
See TracTickets
for help on using tickets.
The attached screen shot shows where the update hangs.