-
Notifications
You must be signed in to change notification settings - Fork 34
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
Safeguarding app silo #76
base: main
Are you sure you want to change the base?
Conversation
Why is this incompatible? Because these policies only apply to UWP applications? Will they be compatible with Win32 in the future? |
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
docs/packaging/Risky-capabilities.md
Outdated
@@ -0,0 +1,30 @@ | |||
# Risky Capabilities | |||
|
|||
This page specifically focuses on capabilities that are incompatible with win 32 app isolation. The following capabilities can lower the security offered by win32 app isolation and application developers should refrain from using them when onboarding to win32 app isolation. |
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.
Break this line - do not write a super long line in md file. Also I believe the official spelling is Win32 app isolation
.
docs/packaging/Risky-capabilities.md
Outdated
|
||
This page specifically focuses on capabilities that are incompatible with win 32 app isolation. The following capabilities can lower the security offered by win32 app isolation and application developers should refrain from using them when onboarding to win32 app isolation. | ||
|
||
* "uiAccess" |
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.
Why quoting the capability? It's probably better to use ` instead of ". That's how we do it in other docs.
Thank you, @tiangao-ms. I have made changes according to your suggestions. |
First draft after receiving Ryan's input.