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

New kid on the block: undetected plutonium #101

Open
najamelan opened this issue Apr 23, 2020 · 2 comments
Open

New kid on the block: undetected plutonium #101

najamelan opened this issue Apr 23, 2020 · 2 comments
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@najamelan
Copy link

This is a crate that allows calling unsafe code without the unsafe keyword. It specifically works to undermine cargo-geiger detection.
I have added it in my cargo-deny config, but it's probably good that cargo geiger prints a big warning on every crate that has this in their dependency graph.

Author also wants to disable forbid(unsafe). The danger seems lesser because forbid only works in the local crate, so I don't really see the point, but it could be a tool to insert malicious code in another library undetected.

@najamelan najamelan changed the title New kid on the block: plutonium New kid on the block: undetected plutonium Apr 23, 2020
@alex
Copy link
Contributor

alex commented Apr 23, 2020

Seems like the solution isn't in cargo-geiger, but rather to have cargo-audit flag it?

@anderejd
Copy link
Contributor

Thanks for the report!

This is related to #102

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants