Skip to content
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

Check if we really need com.apple.security.cs.allow-unsigned-executable-memory on macOS #45677

Closed
janvorli opened this issue Dec 7, 2020 · 0 comments · Fixed by #51294
Closed
Assignees
Milestone

Comments

@janvorli
Copy link
Member

janvorli commented Dec 7, 2020

We are also using com.apple.security.cs.allow-jit, which seems to be sufficient. We should verify if that's the case and remove the com.apple.security.cs.allow-unsigned-executable-memory if it is not needed.

@janvorli janvorli added this to the 6.0.0 milestone Dec 7, 2020
@janvorli janvorli self-assigned this Dec 7, 2020
@Dotnet-GitSync-Bot Dotnet-GitSync-Bot added the untriaged New issue has not been triaged by the area owner label Dec 7, 2020
@janvorli janvorli removed the untriaged New issue has not been triaged by the area owner label Dec 8, 2020
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Apr 15, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label May 21, 2021
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jun 15, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jun 16, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Jul 16, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

2 participants