Project

General

Profile

Actions

Bug #611

closed

Firmware upgrade error: "There has been an error verifying the signature on this image."

Added by Michael Welter over 14 years ago. Updated over 13 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Upgrade
Target version:
-
Start date:
05/21/2010
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

Whenever I attempt to upgrade the firmware I get the below error.

"There has been an error verifying the signature on this image."

The error occurs when performing an auto update. The same warning is given when performing a manual firmware upgrade though the upgrade will work. Since there is a workaround it isn't a big deal but with the daily builds it would be nice to have an auto update working.

I'll do some troubleshooting tonight to see if I can find the root cause. I did not see it reported elsewhere so I'm wondering if a bug in 32\64 bug in verify_digital_signature()

Actions #1

Updated by Jim Pingle over 14 years ago

The snapshots are not signed.

Go to the Updater Settings tab and check the box to ignore the image signing.

Actions #2

Updated by Jim Pingle over 14 years ago

  • Status changed from New to Rejected
Actions #3

Updated by Michael Welter over 14 years ago

Hi Jim, Thanks for the response. I should have mentioned. I already have "Allow to update the system with auto-updater and images with no signature." enabled already.

I'm having a few other issues (several binaries missing, i.e. WOL). I'm going to do a full install and see if the problem persists. I may have caused an issue when mass replacing ip2long while troubleshooting.

Actions #4

Updated by Filipe Vieira over 13 years ago

This problem occurs on pfSense 2 RC3. I have checked "Allow auto-update firmware images with a missing or invalid digital signature to be used. " and still can't apply an update. Maybe you should make a refresh button.

Actions #5

Updated by Filipe Vieira over 13 years ago

It's a refreshing issue. If you chenga the update url to something than change it back, it works.

Actions

Also available in: Atom PDF