microsoft / microsoft/msix-packaging
[Feature Request] Allow disabling the sandbox for an application.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Project
MSIX SDK or Win7Msix
Describe the bug
As https://github.com/safing/portmaster-packaging/issues/44#issuecomment-1700988411 explains:
If I correctly understand, MSIX only runs in a sandboxed container and thus is unsuitable for Portmaster, which comes with a kernel driver - pretty much the opposite.
This prevents a myriad of applications using this format (corroberated by issues for similar projects, like https://github.com/flatpak/flatpak/issues/1699#issue-325376226) instead forcing them to be distributed in legacy installation formats like .MSI, since .APPX is even worse in this regard.
Platform
All, but primarily Windows 11 Home, Pro, and Enterprise.
Additional context
https://github.com/microsoft/msix-packaging/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+disable+sandbox returned 0 results.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or entry points. Start by reviewing the MSIX sandbox constraints and the linked Portmaster and Flatpak discussions, then determine whether disabling the sandbox is supported and where the behavior would be validated. Done requires a defined, supported application-level way to run without the sandbox.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100