Re: Security Updates
On Wed 09 Mar 2022 at 21:46:45 (-0500), Greg Wooledge wrote:
> On Wed, Mar 09, 2022 at 08:28:39PM -0500, Dan Ritter wrote:
> > Dimitrios Papanikolaou wrote:
> > >
> > > I have Debian 10 (buster) installed in my Nodes.
> > > I use the sec repo:
> > >
> > > deb http://security.debian.org/debian-securitybuster/updates main contrib non-free
> >
> > I hope there is another / between security and buster.
>
> You mean a space.
>
> > > This is what I have. But can you explain me. Why I am not getting the latest security updates?
>
> What specific update did you expect to see, that you did not get?
>
> > Today you should be getting a new linux kernel.
>
> In buster? It's not vulnerable to "dirty-pipe". That vulnerability
> was introduced in Linux 5.8, and buster has a 4.x kernel.
Start-Date: 2022-03-07 08:23:15
Commandline: apt-get upgrade
Upgrade: firefox-esr-l10n-en-gb:amd64 (91.6.0esr-1~deb10u1, 91.6.1esr-1~deb10u1), firefox-esr:amd64 (91.6.0esr-1~deb10u1, 91.6.1esr-1~deb10u1)
End-Date: 2022-03-07 08:23:42
… so the previous browser version ran for about 25 days, …
Start-Date: 2022-03-09 12:14:48
Commandline: apt-get upgrade
Upgrade: linux-libc-dev:amd64 (4.19.208-1, 4.19.232-1), linux-compiler-gcc-8-x86:amd64 (4.19.208-1, 4.19.232-1), linux-doc:amd64 (4.19+105+deb10u13, 4.19+105+deb10u14), linux-source:amd64 (4.19+105+deb10u13, 4.19+105+deb10u14), linux-doc-4.19:amd64 (4.19.208-1, 4.19.232-1), linux-kbuild-4.19:amd64 (4.19.208-1, 4.19.232-1), linux-config-4.19:amd64 (4.19.208-1, 4.19.232-1), linux-source-4.19:amd64 (4.19.208-1, 4.19.232-1)
End-Date: 2022-03-09 12:15:10
Start-Date: 2022-03-09 12:22:09
Commandline: apt-get dist-upgrade
Install: linux-headers-4.19.0-19-common:amd64 (4.19.232-1, automatic), linux-headers-4.19.0-19-amd64:amd64 (4.19.232-1, automatic), linux-image-4.19.0-19-amd64:amd64 (4.19.232-1, automatic)
Upgrade: linux-image-amd64:amd64 (4.19+105+deb10u13, 4.19+105+deb10u14), linux-headers-amd64:amd64 (4.19+105+deb10u13, 4.19+105+deb10u14)
End-Date: 2022-03-09 12:23:47
… and 5 months for the previous kernel. Could be coincidental.
Cheers,
David.
Reply to: