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

Review OpenScanHub results for libdnf #1659

Open
ppisar opened this issue Apr 25, 2024 · 2 comments
Open

Review OpenScanHub results for libdnf #1659

ppisar opened this issue Apr 25, 2024 · 2 comments
Labels
Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take

Comments

@ppisar
Copy link
Contributor

ppisar commented Apr 25, 2024

Fedora scanned F41 critical packages for insecure pieces of source code https://lists.fedoraproject.org/archives/list/[email protected]/thread/ZNWA2K3H6OS3LFJOTA5H4FJJC64EBLRK/ Results are at https://svashisht.fedorapeople.org/f41-22-Apr-2024/. There are some findings for libdnf. It would be great to review and the address true positives.

@jan-kolarik jan-kolarik added the Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take label May 2, 2024
@github-project-automation github-project-automation bot moved this to Backlog in DNF team May 2, 2024
@siteshwar
Copy link

A more recent report is available at https://svashisht.fedorapeople.org/f41-03-Jul-2024/

But it contains high number of false positives due to cppcheck warning about limiting analysis of branches. It should be fixed in the future mass scans.

@jan-kolarik jan-kolarik changed the title Review OpenScanHub resuls for libdnf Review OpenScanHub results for libdnf Sep 2, 2024
@siteshwar
Copy link

Report for Fedora 42 (rawhide) is available at https://svashisht.fedorapeople.org/openscanhub/mass-scans/f42-13-Nov-2024/, it significantly reduces number of false positives.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Triaged Someone on the DNF 5 team has read the issue and determined the next steps to take
Projects
Status: Backlog
Development

No branches or pull requests

3 participants