Skip to content
This repository has been archived by the owner on Jan 28, 2022. It is now read-only.

Environment Configuration: Design and planning #4

Open
MouriNaruto opened this issue Dec 7, 2018 · 1 comment
Open

Environment Configuration: Design and planning #4

MouriNaruto opened this issue Dec 7, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@MouriNaruto
Copy link
Contributor

MouriNaruto commented Dec 7, 2018

Background

Alias is mentioned in #2, but zsudo still should have a mechanism about the Environment Configuration for the alias file to include.

Environment Configuration Design

Environment Configuration File

Key Type Details

Plan

@MouriNaruto
Copy link
Contributor Author

In my opinion, the Environment Configuration should include the following configuration items.

  • Token
    • Source (For example, from TrustedInstaller, from current process token or etc.)
    • Privileges (You can require, remove, disable, enable given privileges in the source token.)
    • IL (You can set the Integrity Level of the source token.)
    • AppContainer
      • Create or specify a AppContainer
      • Capabilties (You can set given capabilties. )
  • Job Object
    • Memory limit (Workingset and etc.)
    • I/O limit (Windows 10 Only.)
    • Network bandwidth limit (Windows 10 Only.)
  • Process
    • Process priority (Set or default.)
    • Current Directory (Set or default.)
    • Environment Variables (Set or default.)
    • Run on given CPU cores (Set or default.)
    • Run on given NUMA nodes (Set or default.)
  • Actions
    • BeforeRun
    • AfterRun

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant