Skip to content
This repository has been archived by the owner on May 31, 2023. It is now read-only.

Threshold secret sharing for data (or metadata) #14

Open
Intensity opened this issue Mar 31, 2017 · 1 comment
Open

Threshold secret sharing for data (or metadata) #14

Intensity opened this issue Mar 31, 2017 · 1 comment

Comments

@Intensity
Copy link

Divide the data into n chunks, any k of which are able to recover the information (but with fewer than k shares, no information on the original data can be discerned). An example is Shamir's secret sharing.

This could be combined with other processors. The data payload could be split between a few cloud providers. By metadata, I mean for example an index or an ephemeral symmetric key. But the more common case could be to apply threshold secret sharing to the stream.

@Roman2K
Copy link
Owner

Roman2K commented Apr 2, 2017

Hi @Intensity. Sorry for the late reply, my notifications were disabled 🙈.

Indeed, that processing you suggest would take the form of a two new procs, one for splitting into parts (like parity), one for joining them (like uparity).

I don't need such a proc, so I must admit I don't have the motivation to invest time in it. Would you?

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

No branches or pull requests

2 participants