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

Design permissions system #16

Open
creationix opened this issue Jan 26, 2016 · 1 comment
Open

Design permissions system #16

creationix opened this issue Jan 26, 2016 · 1 comment

Comments

@creationix
Copy link
Collaborator

It would be great to have a universal capabilities system for authenticated users. Scripts will have a list of required permissions to run the scripts and primitives like run command, spawn tty, and browse/edit fs will also have permissions.

We need a profile that's read-only for people who don't want the agent ever making changes (to eventually migrate monitoring agent over).

One idea is to have a hard-coded security profile override (like a umask in filesystems) that's part of the agent's local config on disk. This will limit what the agent can do no matter what is asked over the wire through AEPs.

We should review this permissions system with the managed security folks as well to get more eyes on it.

@creationix creationix modified the milestone: Scripts System Jan 26, 2016
@creationix
Copy link
Collaborator Author

  • Need to design the actual permissions/capabilities.
  • Should also optionally have white-list of scripts/commands to run.

@creationix creationix removed this from the Scripts System milestone Mar 24, 2016
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

1 participant