CVE-2022-23451: RESERVED
--
The output might be a bit terse, but the above ids are known elsewhere,
check the references in the tracker. The second part indicates the status
of that id in the tracker at the moment the script was run.
Stefan Fritsch writes:
> # cat /etc/apt/apt.conf.d/11-default-release
> APT::Default-Release "bullseye";
Just don't do that. It breaks all normal preferences and will end up
preferring "bullseye" over anything else. Including
"bullseye-security".
Use preferences instead if you need to tweak
On 22.01.22 11:09, Stefan Fritsch wrote:
*** 5.10.84-1 990
The 990 looks like pinning for me.
Best regards
Ulf
* [Sat, Jan 22, 2022 at 11:09:20AM +0100] Stefan Fritsch:
I think the bullseye-security codename should be "bullseye" instead.
Or am I missing something
The repo naming scheme has changed with bullseye. I do not have the
announcement at hands, however the old '/updates' is now
'-security',
Hi Viktor,
Am 22.01.22 um 11:34 schrieb SZÉPE Viktor:
Idézem/Quoting Stefan Fritsch :
I have noticed that the latest linux security update is not installed
on my box. The package is available in
# apt-cache policy linux-image-amd64
linux-image-amd64:
Installed: 5.10.84-1
Candidate:
Idézem/Quoting Stefan Fritsch :
Hi,
I have noticed that the latest linux security update is not
installed on my box. The package is available in
# apt-cache policy linux-image-amd64
linux-image-amd64:
Installed: 5.10.84-1
Candidate: 5.10.84-1
Version table:
5.15.15-1 500
Hi,
I have noticed that the latest linux security update is not installed on
my box. The package is available in
# apt-cache policy linux-image-amd64
linux-image-amd64:
Installed: 5.10.84-1
Candidate: 5.10.84-1
Version table:
5.15.15-1 500
500
7 matches
Mail list logo
