A Proxmox node runs its own kernel under every guest, which makes it the host where a kernel CVE's preconditions matter most. ProxmoxDriver mixes in KernelFactsMixin (napalm-device-types 2.1.0) and supplies only the transport, the existing exec path.
Depends on the napalm-device-types PR (feat/kernel-facts). For netOrk #268.
A Proxmox node runs its own kernel under every guest, which makes it the host where a kernel CVE's preconditions matter most. `ProxmoxDriver` mixes in `KernelFactsMixin` (napalm-device-types 2.1.0) and supplies only the transport, the existing exec path.
Depends on the napalm-device-types PR (`feat/kernel-facts`). For netOrk #268.
A Proxmox node runs its own kernel under every guest, which makes it the host
where a kernel CVE's preconditions matter most. ProxmoxDriver mixes in
KernelFactsMixin from napalm-device-types and supplies only the transport,
the existing exec path.
Requires napalm-device-types 2.1.0.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A Proxmox node runs its own kernel under every guest, which makes it the host where a kernel CVE's preconditions matter most.
ProxmoxDrivermixes inKernelFactsMixin(napalm-device-types 2.1.0) and supplies only the transport, the existing exec path.Depends on the napalm-device-types PR (
feat/kernel-facts). For netOrk #268.