-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Detect usage of ICryptoTransform that would be thread-unsafe #956
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
Detect usage of ICryptoTransform that would be thread-unsafe #956
Conversation
…t ICryptoTransform that would be thread-unsafe, and potentially result in incorrect cryptographic results.
hvitved
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you very much for your contribution @raulgarciamsft, this is great stuff. I have a couple of comments, let me know what you think.
hvitved
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one more thing, and then I'm happy.
jf205
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @raulgarciamsft.
I have reviewed the qhelp file on behalf of the Semmle documentation team.
I've made a few suggestions on how I think it could be improved - hopefully they don't change the intended meaning.
Let me know if you have any questions.
Thanks!
|
The updated documentation LGTM. Thanks. |
Adding a new rule for detecting usage of static objects that implement ICryptoTransform that would be thread-unsafe, and potentially result in incorrect cryptographic results.