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

Red October's basic access control mechanism should be monotone #119

Open
jkroll-cf opened this issue Jan 21, 2016 · 0 comments · May be fixed by #134
Open

Red October's basic access control mechanism should be monotone #119

jkroll-cf opened this issue Jan 21, 2016 · 0 comments · May be fixed by #134

Comments

@jkroll-cf
Copy link
Contributor

Currently, if you delegate and specify users who can decrypt, Red October will only allow those users to make successful decryptions for secrets in the bailiwick of the delegation. However, if you specify an empty users string, Red October abdicates any checking of the user calling decrypt. This nonlinear behavior is not expected, and should be fixed. The ability for anyone to decrypt should be preserved as its own option and should be controlled by metadata on delegation state instead of by overloading the users list.

@APTy APTy linked a pull request Apr 13, 2016 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant