Unsafe block Cross-Tracking and Matching #303
pinkforest
started this conversation in
Ideas
Replies: 2 comments
-
Some pieces of prior work that may be relevant are |
Beta Was this translation helpful? Give feedback.
0 replies
-
Converting this to discussion |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently it's a bit of effort of finding the needle from the haystack to figure out whether the output - which either have unsafe or don't have the unsafe code not allowed bit on - have been audited in any way so the information that the Geiger spits out can be a bit hellscape to understand thus has less value.
Nor there is a standard workflow to keep track of unsafe code blobs as to commenting to enable the maintainers to do the right thing with the unsafe code - everyone does it differently and you have to parse a lot of behind the scenes to know what is going on and even then probably doens't give any clear idea.
I've discussed this in Discord #crypto-and-security as well as in the cargo-crev matrix to come to find and suggest below.
Findings
Idea
This would go long way to allow devs to insert hookpoints for public commenting on any unsafe blocks and for automating the verification that at least some tracking issue is out there...
#![geiger(unsafe_tracker_base_url = "https://github.com/user/repo/issue/<default_unsafe_issue>")] #![geiger(unsafe_tracker = "https://github.com/user/repo/issue/<relevant_unsafe_issue>")]
Beta Was this translation helpful? Give feedback.
All reactions