Open
Milestone

Separe stack process with OS bundaries

Detach in new process the entire stack and run with a different managed user permission with specific limits like:


manager / host machine
        ↓
Staxis runtime + stack finale
        ↓
software applicativo potenzialmente corrotto

or better:

operator / installer
    creates or chooses "staxis-runtime"
    grants only required folder/network permissions
            ↓
Staxis manager
    launches the stack under that pre-existing identity
            ↓
restricted Staxis runtime

--- 

so...

Staxis runtime permissions

read-only:
- system-core
- system-lrpcks
- application source
- public assets
- configuration snapshot

read/write:
- server-logs
- system-temp
- explicit uploads/data folders

denied:
- repository metadata and Git credentials
- manager files
- parent folders
- arbitrary OS paths
- package installation tools
- shell execution, unless explicitly required

network:
- configured inbound ports
- optional restricted outbound access

Staxis shouldn't have to “invent a user,” but in the future it may offer an optional launcher that says, “I’m launching this stack using a pre-provisioned runtime account.” That’s a responsibility

  • Work items 0
  • Merge requests 0
  • Participants 0
  • Labels 0
Loading
Loading
Loading
Loading
0% complete
0%
Start date
No start date
None
Due date
No due date
0
Work items 0
Open: 0 Closed: 0
0
Merge requests 0
Open: 0 Closed: 0 Merged: 0
0
Releases
None
Reference: staxis-platform%"Separe stack process with OS bundaries"