Closed michaelcfanning closed 2 years ago
@shaopeng-gh. @marmegh, easy issue to pick up. If we wanted to be scrupulous, we could add the old rule name as a deprecated friendly name. This might require a plug-in architecture change to BinSkim, glad to discuss this with you if you'd like to pursue that.
@michaelcfanning, would this be strictly updating the friendly name or would we also be looking to rename the class?
We would want to comprehensively update every occurrence of the old name to the new, including class names file names, source code comments, etc. :)
In theory, we would eventually retain a single reference to the old name, in some new property hanging off a skimmer, DeprecatedRuleNames
. This property would be consumed by the logger in order to emit the deprecated rule name when it creates SARIF rule table entries. This scaffolding does not exist, and we should first look at the SARIF SDK (specifically, the Sarif.Driver project) to think about adding it. So let's separate the two workstreams (and I will follow up with you offline on the SARIF SDK possibility. I think the simple rule id rename s/be pretty straightforward).
The existing rule name sounds extremely generic. The new rule name is intended to make it a bit clearer that this rule is enforcing a specific Microsoft compiler security option, its '/sdl' switch.