Date: Fri, 10 Aug 2012 14:06:56 +0200 (CEST) From: "Roberto" <robertot@redix.it> To: freebsd-security@freebsd.org Subject: RE: getting the running patch level Message-ID: <1510.87.4.128.224.1344600416.squirrel@mail.redix.it:443> In-Reply-To: <001701cd7648$c2520350$46f609f0$@com> References: <31946.192.168.0.107.1344505442.squirrel@mail.redix.it:443> <0B65D7562F9DA04FAC3F15C508BF67136B90E09E1F@ESESSCMS0355.eemea.ericsson.se> <33584.192.168.0.107.1344519530.squirrel@mail.redix.it:443> <001701cd7648$c2520350$46f609f0$@com>
next in thread | previous in thread | raw e-mail | index | archive | help
So as far I understand, if the kernel is not updated by the update process, it is not possible to get via "uname" the currently patch level. I also read about put some syscall to return from the kernel the current patch level, but still this solution is "bound" to the kernel modification, which could be not in all cases; in my opinion, why should the kernel keep track of user space packages ? in other word, if freebsd-update change a ssh package (just an example) why this operation should have side effects with the kernel ? But this is just my opinion. I also think this task (keeping track of patch level) should better related to the command freebsd-update itself, should not ? could the update system (that include freebsd-update) keep track of what is the current system patching state ? and why not all previous package updates ? still these are my ideas... Roberto On Thu, August 9, 2012 18:05, Cedric GROSS wrote: > Hello Roberto, > > In fact "uname -a" report patch level BUT if you update your system by > freebsd-update, patch level could be an old one. > As discuss here http://forums.freebsd.org/archive/index.php/t-20154.html > > Regards > Cedric
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1510.87.4.128.224.1344600416.squirrel>