2.3 Update image "not digitally signed"?
-
I downloaded and tried to install the 2.3 update files manually and I got the following warning:
This image is not digitally signed.
This means that the image you uploaded is not an official/supported image and may lead to unexpected behavior or security compromises. Only install images that come from sources that you trust, and make sure that the image has not been tampered with.Do you want to install this image anyway (on your own risk)?
Is that the expected behavior?
The file I downloaded is "pfSense-CE-Full-Update-2.3-RC-amd64-latest.tgz" from "https://snapshots.pfsense.org/amd64/pfSense_RELENG_2_3/updates/". I also downloaded the sha256 file and the checksums match. I did not expect to get the above warning so I aborted the update.
-
Snapshot builds are not signed. The RC builds from the download links on the blog post are signed. It's fine to use either/or. We put out a set that's signed partially to test the entirety of the release process, partially so people have a known-verified version available to try.
-
If I installed from a memstick, does it matter if I use the CD or memstick version? I am manually updating via the web gui, so I won't be plugging in a memstick/cd btw.
-
Neither, you want the full update file in that case. Use the link for Updates on the blog post if you're going that route.
-
Hmm, well the blog post still requires you to select a platform: CD/memstick/Nano.
I selected the CD and it worked out fine.
-
Oh, right, it's the same update file regardless of how you installed it. We should clarify that. Most people update via auto-update so that page doesn't get used much for update purposes (outside things like RC).