-
Notifications
You must be signed in to change notification settings - Fork 4
Gendarme.Rules.Security.Cas.DoNotExposeFieldsInSecuredTypeRule(git)
Sebastien Pouliot edited this page Mar 2, 2011
·
1 revision
Assembly: Gendarme.Rules.Security.Cas
Version: git
The rule checks for types that are secured by Demand or LinkDemand but also expose visible fields. Access to these fields is not covered by the declarative demands, opening potential security holes.
Bad example:
[SecurityPermission (SecurityAction.LinkDemand, ControlThread = true)]
public class Bad {
}
Good example (InheritanceDemand):
[SecurityPermission (SecurityAction.LinkDemand, ControlThread = true)]
[SecurityPermission (SecurityAction.InheritanceDemand, ControlThread = true)]
public class Correct {
}
Good example (sealed):
[SecurityPermission (SecurityAction.LinkDemand, ControlThread = true)]
public sealed class Correct {
}
- Before Gendarme 2.2 this rule was part of Gendarme.Rules.Security and named TypeExposeFieldsRule.
You can browse the latest source code of this rule on github.com
Note that this page was autogenerated (3/17/2011 1:55:44 PM) based on the xmldoc
comments inside the rules source code and cannot be edited from this wiki.
Please report any documentation errors, typos or suggestions to the
Gendarme Mailing List. Thanks!