What happened:
When scanning with linux-kernel-cataloger, Linux Kernel images with the names bzImage-* and zImage-* are skipped by the cataloger.
Currently the cataloger only detects:
kernel-*
vmlinux-*
vmlinuz-*
What you expected to happen:
bzImage and zImage is a common name used for Linux Kernel images, especially in embedded systems. They are identical to vmlinuz but just have a different name.
Steps to reproduce the issue:
Scan a filesystem that contains a Linux Kernel image with the name bzImage-* or zImage-*.
Anything else we need to know?:
I've addressed this bug in #4751 .
Environment:
- Output of
syft version: syft 1.42.3
- OS (e.g:
cat /etc/os-release or similar):
PRETTY_NAME="Ubuntu 24.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.3 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo
What happened:
When scanning with linux-kernel-cataloger, Linux Kernel images with the names
bzImage-*andzImage-*are skipped by the cataloger.Currently the cataloger only detects:
kernel-*vmlinux-*vmlinuz-*What you expected to happen:
bzImageandzImageis a common name used for Linux Kernel images, especially in embedded systems. They are identical tovmlinuzbut just have a different name.Steps to reproduce the issue:
Scan a filesystem that contains a Linux Kernel image with the name
bzImage-* orzImage-*.Anything else we need to know?:
I've addressed this bug in #4751 .
Environment:
syft version:syft 1.42.3cat /etc/os-releaseor similar):