-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Enable CET shadow stack compatibility in apphost/singlefilehost by default
#103007
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
Conversation
|
Tagging subscribers to this area: @vitek-karas, @agocke |
janvorli
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.
LGTM, thank you!
mangod9
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.
Thanks for implementing this. We should keep an eye on CI, we had noticed that the CET specific CI was failing with new EH enabled, so wondering if that would affect a wider spectrum after this merges.
AaronRobinsonMSFT
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.
![]()
|
@elinor-fung please don't merge this change in yet. I was investigating a CET test leg failure yesterday and found a problem with the shadow stack and the new exception handling that needs to be addressed before this change gets in. |
|
@elinor-fung my CET fix is merged in, so please feel free to merge this in once the CI is green. |
|
Thanks, @janvorli! |
Enable CET shadow stack compatibility in apphost/singlefilehost by default
apphostandsinglefilehostwith/cetcompat(shared libraries are already being built with this flag)HostWriter.CreateAppHostThis change makes it so that a user's app will have CET compatibility enabled by default (for Windows x64). There will be a corresponding change on the SDK side such that it can be disabled with
<CetCompat>false</CetCompat>.cc @dotnet/appmodel @janvorli @mangod9