From f7ca79c16e7ff8254d6cc543a76df8528a44e005 Mon Sep 17 00:00:00 2001 From: panda Date: Sun, 1 Aug 2021 01:23:48 +0200 Subject: [PATCH] added to readme --- README.md | 6 ++++++ gpg-quorum_4of5.sh => _Examples/gpg-quorum_4of5.sh | 0 2 files changed, 6 insertions(+) rename gpg-quorum_4of5.sh => _Examples/gpg-quorum_4of5.sh (100%) diff --git a/README.md b/README.md index 87b2f30..00cb8c6 100644 --- a/README.md +++ b/README.md @@ -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: diff --git a/gpg-quorum_4of5.sh b/_Examples/gpg-quorum_4of5.sh similarity index 100% rename from gpg-quorum_4of5.sh rename to _Examples/gpg-quorum_4of5.sh