Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More data in manifest files #53

Open
mssalvatore opened this issue Aug 21, 2020 · 1 comment
Open

More data in manifest files #53

mssalvatore opened this issue Aug 21, 2020 · 1 comment
Labels

Comments

@mssalvatore
Copy link
Contributor

Define a new format for manifest files that includes the release codename, source package for each binary, src and binary package versions, and installation status.

Something along the lines of,

(lsb_release -c && dpkg-query -f '${binary:Package},${Source:Package},${Source:Version},${Status}\n' -W) | tee manifest.txt

could be used to generate such as file.

The key is keeping it simple enough that someone can't type it in, but also having it contain all the necessary data. We could also provide a manifest_generator that generates the manifests. The whole point of manifests is that you don't need to install CVEScan in order to scan your systems, so this is a somewhat difficult balance to achieve.

oholiab added a commit to oholiab/sec-cvescan that referenced this issue Aug 21, 2020
This allows manifests to have the release codename explicitly
input as the first line, and falls back to the heuristic method of
deterimining it from package versions as postulated in canonical#53
@mssalvatore
Copy link
Contributor Author

mssalvatore commented Oct 9, 2020

After spending some more time looking at dpkg-query, I think that

(lsb_release -c && dpkg-query -f '${db:Status-Abbrev},${binary:Package},${Version},${source:Package},${Source:Version}\n' -W) | tee manifest.txt

is probably a superior way to format the manifest file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant