added to readme
This commit is contained in:
parent
4aca97019a
commit
f7ca79c16e
2 changed files with 6 additions and 0 deletions
|
@ -5,9 +5,13 @@ or: digital testament encryption management
|
|||
### needs:
|
||||
|
||||
Sometimes we find ourselves managing pieces of software/infrastructure/etc with all the passwords/knowledge and everything well encrypted,
|
||||
|
||||
the question I've asked myself is: what if for some reason we unwillingly disappear, what happens to all these data?
|
||||
|
||||
Maybe it's a shared service with others but on your machines, maybe it's your data that should be nice to make accessible to your significant other (but the other does not have a tech knowledge enough to be able to do it).
|
||||
|
||||
So I wanted something capable of encrypting a file/archive/furryporn/whatever in a way that it was encrypted for N persons but only a willi quorum of X persons was needed to decypher it.
|
||||
|
||||
I looked into "Shamir secret sharing" but I find that generating a new secret that should be distributed among the interested parties could be the key for failure.
|
||||
|
||||
### requirements:
|
||||
|
@ -67,6 +71,8 @@ I don't have a clear idea about that right now.
|
|||
|
||||
### customization:
|
||||
|
||||
see the example in _Examples/gpg-quorum_4of5.sh
|
||||
|
||||
if you want to increase the number of people needed to decrypt the file to 4 for example,
|
||||
edit this block of code from:
|
||||
|
||||
|
|
Loading…
Reference in a new issue