You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first, thank you for this implementation of SSSS, which is one of the nicest and most accessible I've seen on the web.
Here the use case : We're 3 people sharing a common space, and we installed cameras. Our camera system only allows 1 admin (email + password, no 2FA). We do NOT want anybody accessing the recordings unless someone reports something being stolen.
We want to create an admin password so that each member only knows parts of it, and never the full password. Person 1 will have the 4 first characters, person 2 the next 4, and person 3 the last four characters. The email will be a gaggle email that will send all emails to us, also secured by this password. Thus preventing a stealth "forgot password" method.
When an item is reported as stolen, every member regroups and they, each after one other, enter their string into the Camera app an can resolve the issue together.
Now, if one member IS the robber, then they will not disclose their part, by faking it's correct when it's not.
Your implementation of SSSS is good for that, but it needs some options for this kind of use case. As each member "ENTERS" its own strings one after another, the next member to add its series of trings should NOT see the firsts parts of the secret.
So I guess :
1 . Would it be possible to add a button/switch next to the SECRET field to hide its content (and, for example, lock/grey the switch button it for 1 minute so no one can intervene?)
2. A way/option to display the QR codes 1 by 1, so each member can, 1 after the other, take a picture of the one for them, without the need of a printer.
I don't know if everything makes sense here.
thank you for your implementation and your software.
The text was updated successfully, but these errors were encountered:
first, thank you for this implementation of SSSS, which is one of the nicest and most accessible I've seen on the web.
Here the use case : We're 3 people sharing a common space, and we installed cameras. Our camera system only allows 1 admin (email + password, no 2FA). We do NOT want anybody accessing the recordings unless someone reports something being stolen.
We want to create an admin password so that each member only knows parts of it, and never the full password. Person 1 will have the 4 first characters, person 2 the next 4, and person 3 the last four characters. The email will be a gaggle email that will send all emails to us, also secured by this password. Thus preventing a stealth "forgot password" method.
When an item is reported as stolen, every member regroups and they, each after one other, enter their string into the Camera app an can resolve the issue together.
Now, if one member IS the robber, then they will not disclose their part, by faking it's correct when it's not.
Your implementation of SSSS is good for that, but it needs some options for this kind of use case. As each member "ENTERS" its own strings one after another, the next member to add its series of trings should NOT see the firsts parts of the secret.
So I guess :
1 . Would it be possible to add a button/switch next to the SECRET field to hide its content (and, for example, lock/grey the switch button it for 1 minute so no one can intervene?)
2. A way/option to display the QR codes 1 by 1, so each member can, 1 after the other, take a picture of the one for them, without the need of a printer.
I don't know if everything makes sense here.
thank you for your implementation and your software.
The text was updated successfully, but these errors were encountered: