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

Minimum should be made more robust #149

Open
jkroll-cf opened this issue Jun 3, 2016 · 1 comment
Open

Minimum should be made more robust #149

jkroll-cf opened this issue Jun 3, 2016 · 1 comment

Comments

@jkroll-cf
Copy link
Contributor

Currently, the UI will not specify a minimum although it shows what appears to be a default. This leads to situations where users create ciphertexts which can't be decrypted (because they require a minimum of 0 owners and don't get any actual encryptions). This should be handled better from a UX perspective:

  • The UI & backend should only allow valid values of "Minimum" and should require a predicate when Minimum == 0.
  • The UI should offer a dropdown that clearly explains how to use this, to steer people towards not falling into this trap.
    I've seen this happen several (at least 3) separate times, and it's an easy fix.
@jkroll-cf
Copy link
Contributor Author

Additionally, if Minimum > 0 and a predicate is set, the request should be denied in the UI as it isn't clear which policy to apply to the ciphertext.

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

No branches or pull requests

1 participant