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
The receivers of the shares might not know/remember what the threshold is and whether the shares belong together. How about having an extended form of the shares as follows?
<share>[/<threshold>[/identifier]]
The identifier could be specified on the split command line, with a small (32 bit?) randomly generated identifier as the default. This would allow the recipient to be able to distinguish his/her shares.
On combine, the threshold would be read from the first share, if not specified on the command line. Also, thresholds and identifiers, if present, would be compared to reduce the possibility for wrong combinations.
The text was updated successfully, but these errors were encountered:
The receivers of the shares might not know/remember what the threshold is and whether the shares belong together. How about having an extended form of the shares as follows?
<share>[/<threshold>[/identifier]]
The identifier could be specified on the
split
command line, with a small (32 bit?) randomly generated identifier as the default. This would allow the recipient to be able to distinguish his/her shares.On
combine
, the threshold would be read from the first share, if not specified on the command line. Also, thresholds and identifiers, if present, would be compared to reduce the possibility for wrong combinations.The text was updated successfully, but these errors were encountered: