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

dotnet tools do not support differing entitlements than the dotnet muxer on Mac #23640

Open
Tracked by #29436
agocke opened this issue Jan 27, 2022 · 3 comments
Open
Tracked by #29436
Milestone

Comments

@agocke
Copy link
Member

agocke commented Jan 27, 2022

See dotnet/runtime#63952 for context. In this case, a dotnet tool requires more entitlements than dotnet, so it can't be executed using the dotnet muxer. If dotnet tools always use an apphost, then the host should be ad hoc signed, which would allow all requirements.

@ClearScriptLib
Copy link

This issue affects dotnet test as well.

@marcpopMSFT marcpopMSFT removed the untriaged Request triage from a team member label Feb 9, 2022
@marcpopMSFT marcpopMSFT added this to the 7.0.1xx milestone Feb 9, 2022
@marcpopMSFT
Copy link
Member

@agocke Do we have to increase the entitlements for the host created during tool install? Is there risk in setting more entitlements for dotnet?

@agocke
Copy link
Member Author

agocke commented Feb 9, 2022

Is there risk in setting more entitlements for dotnet?

Yeah, those are minimum install requirements for dotnet, so we want that list to be as small as possible. For the dotnet tool, the host that sometimes gets created is ad hoc signed, so it automatically has all entitlements. I believe the improvement here would be to always create and use a host for dotnet tools.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants