Date: Fri, 29 Apr 2016 07:23:23 -0400 From: Stari Karp <starikarp@yandex.com> To: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-16:16.ntp Message-ID: <1461929003.67736.2.camel@yandex.com> In-Reply-To: <9e6342a420259fec7bd21d6222cc6e05@zahemszky.hu> References: <20160429082953.DB31D1769@freefall.freebsd.org> <9e6342a420259fec7bd21d6222cc6e05@zahemszky.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2016-04-29 at 13:13 +0200, gabor@zahemszky.hu wrote: > > > > 2) To update your vulnerable system via a binary patch: > > > > Systems running a RELEASE version of FreeBSD on the i386 or amd64 > > platforms can be updated via the freebsd-update(8) utility: > > > > # freebsd-update fetch > > # freebsd-update install > Both on an i386 and on an amd64 machine, I got: > > ==== > .... > Fetching metadasa signature for 10.3-RELEASE from > update5.freebsd.org... > done > Fetching metadata index.... done > > The update metadata is correctly signed, but > failed an integrity check. > Cowardly refusing to proceed any further. > ==== > > Both machines are VM-s, upgraded from 10.2. > > (Got the same with -s update[23456].freebsd.org, and without -s > option. > > Zahy < Gabor at Zahemszky dot HU > > _______________________________________________ I have the same. I did upgrade FreeBSD 10.2 with freebsd-update to version 10.3: freebsd-version -ku 10.3-RELEASE 10.3-RELEASE FreeBSD 10.3-RELEASE #1: Sun Apr 10 13:48:11 EDT 2016 blabla@morebl a.bla.net:/usr/obj/usr/src/sys/GENERIC amd64 freebsd-version -ku
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1461929003.67736.2.camel>