:: [DNG] unsigned kernels - strange be…
Pàgina inicial
Delete this message
Reply to this message
Autor: Erich Minderlein
Data:  
A: dng
Assumpte: [DNG] unsigned kernels - strange behaviour
Hi

tonight my ansible stopped execution with the message

TASK [Reboot the box if kernel updated] ****************************************
fatal: [*$Hostname*]: FAILED! => {"changed": false, "elapsed": 0, "msg": "Running reboot with local connection would reboot the control node.", "rebooted": false}

Now there are no new kernels to install, because the system is up to date.
Last kernel install was Feb 7 06:49

/ ls -tlah vmlinuz*
lrwxrwxrwx 1 root root 28 Feb 7 06:49 vmlinuz -> boot/vmlinuz-4.19.0-14-amd64
lrwxrwxrwx 1 root root 28 Feb 7 06:49 vmlinuz.old -> boot/vmlinuz-4.19.0-13-amd64
/boot # ls -tlah vmlinuz*
-rw-r--r-- 1 root root 5.1M Jan 30 10:35 vmlinuz-4.19.0-14-amd64
-rw-r--r-- 1 root root 5.1M Nov 28 08:47 vmlinuz-4.19.0-13-amd64

looking at the kernels I find this
dpkg -l 'linux-image-*-unsigned'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                 Version      Architecture Description
+++-====================================-============-============-=================================
un  linux-image-4.19.0-13-amd64-unsigned <none>       <none>       (no description available)
un  linux-image-4.19.0-14-amd64-unsigned <none>       <none>       (no description available)


aptitude shows
  Actions  Undo  Package  Resolver  Search  Options  Views  Help
C-T: Menu  ?: Help  q: Quit  u: Update  g: Preview/Download/Install/Remove Pkgs
aptitude 0.8.11 @ hostname
--\ Not Installed Packages (7)
...
   --\ kernel         Kernel and kernel modules (6)
     --\ main           The main Debian archive (6)
p     linux-image-4.19.0-13-amd64-unsigned                                                                       <none>         4.19.160-2
p     linux-image-4.19.0-13-cloud-amd64-unsigned                                                                 <none>         4.19.160-2
p     linux-image-4.19.0-13-rt-amd64-unsigned                                                                    <none>         4.19.160-2
p     linux-image-4.19.0-14-amd64-unsigned                                                                       <none>         4.19.171-2
p     linux-image-4.19.0-14-cloud-amd64-unsigned                                                                 <none>         4.19.171-2
p     linux-image-4.19.0-14-rt-amd64-unsigned                                                                    <none>         4.19.171-2
                                                            ┌─────────────────────┐
                                                            │Really quit Aptitude?│
                                                            │  [ Yes ]    [ No ]  │
                                                            └─────────────────────┘
These packages are not installed on your computer.
This group contains 7 packages.


What are these unsigned packages for ?

Why does the system want install some unknown kernels as the actual signed package is already installed ?

Three month ago I had a strange collapse of my debian,
as the directory /usr was empty over night.
System was unusable and I made a fresh install of devuan instad of debian.
I planned this anyhow.
Is there something spooky going on ?
Is something compromised on this system ?

--
mit freundlichen Grüßen
with the best(e) regards

cordialement

Erich |\/|inderlei|\|