Skip to content
This repository has been archived by the owner on Jun 18, 2019. It is now read-only.

"Distribute Secret Shards" view does not allow the user to go back to the previous view #46

Open
1 task
garrettr opened this issue Jun 16, 2017 · 2 comments
Milestone

Comments

@garrettr
Copy link
Contributor

Feature Request

Description

If you are in the "Distribute Secret Shards" view, there is no "Back" button that allows you to return to the previous "Create Secret Shards" view. There is a back button, but it says "Home" and takes you back to the start page.

I anticipate users splitting a secret, only to realize they want to modify the secret or the sharing parameters slightly. It would be nice if the user could go back to the previous "Create Secret Shards" view, make a minor modification to the parameters they already set, and then re-create secret shards with the updated parameters.

Of course, there is a serious UX concern, with implications for availability, here: users must not mix shards from two different sets of shards. Without providing some kind of clear messaging to the user, I'm afraid it would be easy for them to unintentionally or accidentally distribute shards from two or more sets, and then be unable to recover their secret at a later date.

User stories

  • To do
@garrettr garrettr added this to the Post-1.0 milestone Jun 16, 2017
@GabeIsman
Copy link
Contributor

I think this is a great point, and will be simple to implement. Perhaps we could address the UX concern by appending a unique string to the suggested file names when saving shares. Either a random nonce or a randomly chosen english adjective would do. That would be a clear reminder that the shares belong to different sets.

@liliakai
Copy link
Contributor

liliakai commented May 8, 2018

Perhaps we could address the UX concern by appending a unique string to the suggested file names when saving shares. Either a random nonce or a randomly chosen english adjective would do. That would be a clear reminder that the shares belong to different sets.

Or a timestamp, or bytes from the public signing key.

However, I'm inclined to punt on this issue until we see it causing trouble a real world use case. Re-filling your sharing params and selecting a file is pretty quick even if you have to do multiple times, and if you're using the textarea for anything other than copy/paste or very trivial hand entry, you might be doing it wrong (per the docs on separation of the secret and the data it protects)...

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

No branches or pull requests

3 participants