$ sudo dnf remove kmod-VirtualBox-$(uname -r)
Dependencias resueltas.
================================================================================
Paquete Arq. Versión Repositorio Tam.
================================================================================
Eliminando:
kmod-VirtualBox-6.5.6-200.fc38.x86_64 x86_64 7.0.10-3.fc38 @@commandline 193 k
Resumen de la transacción
================================================================================
Eliminar 1 Paquete
Espacio liberado: 193 k
¿Está de acuerdo [s/N]?: s
Ejecutando verificación de operación
Verificación de operación exitosa.
Ejecutando prueba de operaciones
Prueba de operación exitosa.
Ejecutando operación
Preparando : 1/1
Eliminando : kmod-VirtualBox-6.5.6-200.fc38.x86_64-7.0.10-3.fc 1/1
Ejecutando scriptlet: kmod-VirtualBox-6.5.6-200.fc38.x86_64-7.0.10-3.fc 1/1
Verificando : kmod-VirtualBox-6.5.6-200.fc38.x86_64-7.0.10-3.fc 1/1
Eliminado:
kmod-VirtualBox-6.5.6-200.fc38.x86_64-7.0.10-3.fc38.x86_64
¡Listo!
------------------------------------------------------------------------------
$ sudo akmods --force
Checking kmods exist for 6.5.6-200.fc38.x86_64 [ OK ]
Building and installing VirtualBox-kmod [ OK ]
$
That akmods command should have returned to the $ prompt after a short time.
yes, that’s how it was
Post the output:
sudo mokutil -t /etc/pki/akmods/certs/public_key.der
mokutil -l | grep -i -e $(modinfo -F sig_key vboxdrv)
find /usr/lib/modules/$(uname -r) -name vbox\* | sort
update-crypto-policies --show
update-crypto-policies --is-applied
update-crypto-policies --check
$ sudo mokutil -t /etc/pki/akmods/certs/public_key.der
/etc/pki/akmods/certs/public_key.der is not enrolled
$ mokutil -l | grep -i -e $(modinfo -F sig_key vboxdrv)
$ (no output)
$ find /usr/lib/modules/$(uname -r) -name vbox\* | sort
/usr/lib/modules/6.5.6-200.fc38.x86_64/extra/VirtualBox/vboxdrv.ko.xz
/usr/lib/modules/6.5.6-200.fc38.x86_64/extra/VirtualBox/vboxnetadp.ko.xz
/usr/lib/modules/6.5.6-200.fc38.x86_64/extra/VirtualBox/vboxnetflt.ko.xz
/usr/lib/modules/6.5.6-200.fc38.x86_64/kernel/drivers/gpu/drm/vboxvideo
/usr/lib/modules/6.5.6-200.fc38.x86_64/kernel/drivers/gpu/drm/vboxvideo/vboxvideo.ko.xz
/usr/lib/modules/6.5.6-200.fc38.x86_64/kernel/drivers/virt/vboxguest
/usr/lib/modules/6.5.6-200.fc38.x86_64/kernel/drivers/virt/vboxguest/vboxguest.ko.xz
/usr/lib/modules/6.5.6-200.fc38.x86_64/kernel/fs/vboxsf
/usr/lib/modules/6.5.6-200.fc38.x86_64/kernel/fs/vboxsf/vboxsf.ko.xz
$ update-crypto-policies --show
DEFAULT
$ update-crypto-policies --is-applied
The configured policy is applied
$ update-crypto-policies --check
The configured policy matches the generated policy
1 Like
You need to enroll the certificate following the instruction:
Tree - rpms/akmods - src.fedoraproject.org
1 Like
What commands should I use to make sure that everything related to VirtualBox is working correctly?
I have followed the steps from Tree - rpms/akmods - src.fedoraproject.org
and now my output is:
sudo mokutil -t /etc/pki/akmods/certs/public_key.der
/etc/pki/akmods/certs/public_key.der is already enrolled
How is that misspelled?
[vek@newbox ~]$ mokutil -l | grep -i -e $(modinfo -F sig_key vboxdrv)
3a:de:7f:97:c8:78:7b:07:fb:3e:d8:d5:dd:e7:d7:73:47:a6:5a:99
[vek@newbox ~]$
It shows that the module is signed by one of the enrolled keys.
Check the loaded modules:
lsmod | grep -e ^vbox
$ lsmod | grep -e ^vbox
vboxnetadp 28672 0
vboxnetflt 40960 0
vboxdrv 692224 2 vboxnetadp,vboxnetflt
Before it seemed to me that an argument was missing for the -e option, however now that I try it again, it works correctly and the output is the following
$ mokutil -l | grep -i -e $(modinfo -F sig_key vboxdrv)
43:a1:50:5c:2c:d8:db:77:a7:ab:99:56:82:6a:d6:ab:28:93:6c:fd
That indicates that the module was not signed.