Does this update actually work? After hitting install and crunching for a while, it showed "firmware installation failed!" at the top.
Log window showed: firmware installation failed! >>> Updating repositories metadata... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. >>> Unlocking package pfSense-kernel-pfSense... done. >>> Downloading upgrade packages... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. Checking for upgrades (5 candidates): ..... done Processing candidates (5 candidates): ... done The following 2 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense: 2.3 -> 2.3_1 [pfSense] ntp: 4.2.8p6 -> 4.2.8p7 [pfSense] The process will require 2 KiB more space. 493 KiB to be downloaded. Fetching pfSense-2.3_1.txz: . done Fetching ntp-4.2.8p7.txz: .......... done Checking integrity... done (0 conflicting) >>> Upgrading necessary packages... Updating pfSense-core repository catalogue... pfSense-core repository is up-to-date. Updating pfSense repository catalogue... pfSense repository is up-to-date. All repositories are up-to-date. Checking for upgrades (5 candidates): ..... done Processing candidates (5 candidates): ... done Checking integrity... done (0 conflicting) The following 2 package(s) will be affected (of 0 checked): Installed packages to be UPGRADED: pfSense: 2.3 -> 2.3_1 [pfSense] ntp: 4.2.8p6 -> 4.2.8p7 [pfSense] The process will require 2 KiB more space. [1/2] Upgrading ntp from 4.2.8p6 to 4.2.8p7... [1/2] Extracting ntp-4.2.8p7: .......... done [2/2] Upgrading pfSense from 2.3 to 2.3_1... [2/2] Extracting pfSense-2.3_1: ... done >>> Removing unnecessary packages... done. >>> Cleanup pkg cache... done. >>> Locking package pfSense-kernel-pfSense... done. On Mon, May 2, 2016 at 8:24 AM, Olivier Mascia <[email protected]> wrote: > > > Le 2 mai 2016 à 16:19, Jason Hellenthal <[email protected]> a > écrit : > > > > Signé partie PGP > > _1 would not be a development release. That would be a patch or an > addendum which I would assume handles the ntp security flaw patched in > recent FreeBSD security release. > > > > https://www.freebsd.org/security/advisories/FreeBSD-SA-16:16.ntp.asc > > > > On May 2, 2016, at 08:54, Olivier Mascia <[email protected]> wrote: > > > > The update check on 2.3-REL GUI offers me 2.3_1, yet I don't see mention > of it on pfsense.org. > > Could it be that my system polls for dev branch releases and not only > released builds? > > Or that the auto-update only revealed the beast before the blog on > pfsense.org? > > Indeed. > > Installed packages to be UPGRADED: > pfSense: 2.3 -> 2.3_1 [pfSense] > ntp: 4.2.8p6 -> 4.2.8p7 [pfSense] > > -- > Meilleures salutations, Met vriendelijke groeten, Best Regards, > Olivier Mascia, integral.be/om > > > _______________________________________________ > pfSense mailing list > https://lists.pfsense.org/mailman/listinfo/list > Support the project with Gold! https://pfsense.org/gold > _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
