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

Need for a Viable Security Scanning Tool #557

Closed
kxyr opened this issue May 21, 2021 · 2 comments
Closed

Need for a Viable Security Scanning Tool #557

kxyr opened this issue May 21, 2021 · 2 comments

Comments

@kxyr
Copy link

kxyr commented May 21, 2021

A security workflow does not currently exist as part of the CI/CD or security workflows in the Rust repository. This is necessary to satisfy the security requirements of open-telemetry/opentelemetry-specification#1333.

CodeQL is the common security scanning tool that is used currently for all of the supported OpenTelemetry language repositories (Go, Java, Javascript, Python, C++, etc.). Unfortunately CodeQL does not offer support for Rust. Thus an alternative would need to be found.

We evaluated different possibilities but there seems to be limited available code scanning tools for Rust that could be integrated with Github Actions. The following code scanning tools for Rust could work:

  • Rust Audit Check. This tool however only checks for reported security vulnerabilities in dependencies

We’d like to better understand the opinions from Rust engineers on a recommended code scanning tool so that one may be added for open-telemetry/oteps#144.

cc @KKelvinLo @alolita

@djc
Copy link
Contributor

djc commented May 22, 2021

I like to use cargo-deny, which will check for vulnerable dependencies but can also help checking for inappropriate licenses and duplicate dependency versions.

@TommyCpp
Copy link
Contributor

Should we also consider adding a license check? I ran a quick check with cargo deny. The only crate that seems to be a problem is ring. It contains a custom LICENSE file. The template in cargo deny describes ring's LICENSE as MIT AND ISC AND OpenSSL. I suppose this is compatible with our repo's license?

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

No branches or pull requests

3 participants