Security: vulnerabilities in what you build¶
kaji checks what you build against Gentoo’s security advisories (GLSAs), tells you which of your builds are affected and what is made from them, and mails the people concerned.
What is checked, and when¶
A package build, when it has succeeded: the packages it built.
A root filesystem, when it has succeeded: from its lock file, the exact list of what is installed, including dependencies that came from a repository.
Each is scanned again whenever what it looks at changes, and at least once a day, which is how a newly published advisory reaches a build that has not changed. The advisories are always the newest, never those of the tree the build was made from: a build from an old tree is exactly the one that needs today’s advisories.
A build or root page has Scan now, which checks it immediately, and says when the next scan is.
The Vulnerabilities list¶
Security > Vulnerabilities lists what was found, worst first.
Column |
Meaning |
|---|---|
Severity |
How serious: high, normal, low. |
Advisory |
The GLSA, linked to Gentoo’s page. |
CVEs |
How many CVE records it covers; the advisory’s page lists them. |
Package and Fixed in |
The affected version, and the version that fixes it. |
Builds |
The package builds it was found in. |
Used by |
What is made straight from where it was found: for a finding in a package build, the root filesystems made from it; for one in a root, the container images and live CDs made from that root. |
Found |
When. |
A package that is in both a build and the root made from it appears twice, once for each scan, with its own Used by.
Fix it¶
Build again with a tree that has the fixed version, then build the root and the image again from the new build. The old findings go when the new scan finds nothing.
Mail¶
Members of the organization that owns a build, and of those that own what is made from it, are mailed about a finding: one mail lists all that are new.