The rpm query now reads %{SOURCERPM}. Each package carries the source rpm's name as source_rpm (perf -> kernel), and leaves it out where rpm names none (gpg-pubkey).
Why: perf, python3-perf and bpftool are built from the kernel's source rpm, and Red Hat's VEX lists them in every kernel CVE. On build-arm-01 (Oracle Linux 9.8) that came to 18 532 findings on these three tools alone. netOrk tells them apart from user space by their source (NetOrk/netork#2394).
Why not source_package: netOrk reads dpkg's source_package as the name a distribution files its verdicts under. That holds for Debian, but not for Oracle or Red Hat, whose records name the binary.
Tests: TestRpmPackages, TestSourceRpmName.
The rpm query now reads `%{SOURCERPM}`. Each package carries the source rpm's name as `source_rpm` (`perf` -> `kernel`), and leaves it out where rpm names none (`gpg-pubkey`).
**Why:** perf, python3-perf and bpftool are built from the kernel's source rpm, and Red Hat's VEX lists them in every kernel CVE. On build-arm-01 (Oracle Linux 9.8) that came to 18 532 findings on these three tools alone. netOrk tells them apart from user space by their source (NetOrk/netork#2394).
**Why not `source_package`:** netOrk reads dpkg's `source_package` as the name a distribution files its verdicts under. That holds for Debian, but not for Oracle or Red Hat, whose records name the binary.
Tests: `TestRpmPackages`, `TestSourceRpmName`.
perf, python3-perf and bpftool are built from the kernel's source rpm, and
Red Hat's VEX lists them in every kernel CVE: 18 532 findings on an Oracle
Linux 9 host's three kernel tools alone. The rpm query now reads
%{SOURCERPM}, and each package carries its name as `source_rpm` (`perf` ->
`kernel`), absent where rpm names none (`gpg-pubkey`).
Not dpkg's `source_package`: netOrk reads that as the name a distribution
files its verdicts under, which holds for Debian and not for Oracle or Red
Hat, whose records name the binary (NetOrk/netork#2394).
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.
The rpm query now reads
%{SOURCERPM}. Each package carries the source rpm's name assource_rpm(perf->kernel), and leaves it out where rpm names none (gpg-pubkey).Why: perf, python3-perf and bpftool are built from the kernel's source rpm, and Red Hat's VEX lists them in every kernel CVE. On build-arm-01 (Oracle Linux 9.8) that came to 18 532 findings on these three tools alone. netOrk tells them apart from user space by their source (NetOrk/netork#2394).
Why not
source_package: netOrk reads dpkg'ssource_packageas the name a distribution files its verdicts under. That holds for Debian, but not for Oracle or Red Hat, whose records name the binary.Tests:
TestRpmPackages,TestSourceRpmName.perf, python3-perf and bpftool are built from the kernel's source rpm, and Red Hat's VEX lists them in every kernel CVE: 18 532 findings on an Oracle Linux 9 host's three kernel tools alone. The rpm query now reads %{SOURCERPM}, and each package carries its name as `source_rpm` (`perf` -> `kernel`), absent where rpm names none (`gpg-pubkey`). Not dpkg's `source_package`: netOrk reads that as the name a distribution files its verdicts under, which holds for Debian and not for Oracle or Red Hat, whose records name the binary (NetOrk/netork#2394).