Project

General

Profile

Actions

Correction #16794

closed

Troubleshooting upgrades documentation points to trusted key file that is outdated.

Added by Lars Lindley 2 days ago. Updated 1 day ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Troubleshooting
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:

Description

In the Force pkg Metadata Update section there is a suggestion to fetch a new trusted key file:
fetch -qo /usr/local/share/pfSense/keys/pkg/trusted/ \
https://raw.githubusercontent.com/pfsense/pfsense/RELENG_2_4_5/src/usr/local/share/pfSense/keys/pkg/trusted/pkg.pfsense.org.20160406

The file referenced contains an outdated file containing a fingerprint starting with 30be.
The current correct fingerprint starts with 2af3a.

Pulling down this incorrect fingerprint makes pkg and pkg-static not trust anything and updating breaks completely.

Actions #1

Updated by Jim Pingle 1 day ago

  • Status changed from New to Rejected

There are multiple keys. The key linked in the document is correct for CE, as it states in the sentence before the link.

That key, however, is not correct for Plus, which is the key you quoted as being "correct".

Actions

Also available in: Atom PDF