-
Use case is mainly as a safety net (backup fido2 device), but could be used for multiple user access.
I figure this could be based on a k in n shared secret algorithm like shamir secret sharing. …
-
**Current Status**
It is only possible to share passwords. But not to unlock one with the knowledge of many people.
**Feature Description**
My first idea is to have a vault, which can only be unl…
-
Under the current scheme, only two backups need to be compromised for someone to gain access to the encrypted data. We _could_ require 3 or more people to collaborate to decrypt a backup. This would b…
-
It's a very small crate / API but this is a non-trivial upgrade. Several types that we've serialized in past ceremonies have been removed so we'll need our own types for the serialization and we'll ne…
flihp updated
1 month ago
-
- First, the documentation should be updated to indicate that both `Create()` and `Combine() `return TWO parameters: _data, error._
- Second, the `Create()` function is returning an array of shards, …
-
When using groups to split a key using shamir secret sharing, modifying a key in any group in `.sops.yaml` will cause the file to be reencrypted after running `updatekeys`. The same is not true when …
-
Currently, we use a custom implementation of SSS (Shamir's Secret Sharing) because there was no standard at the time.
We cannot use SLIP-39, because it does not allow to "split up" an existing BIP-…
-
Hello,
Your Shamir secret sharing code around meet the cryptographic security rules ?
Some details like : integrity checks and side-channel resistance
Recommandations :
*Be side channel r…
-
Hi I love the idea of putting together the possibility to split the secret. Only I've no idea how to put them back together, maybe you can point me in the right direction. thanks Alex
-
While investigating the security of McCallum-Relyea I found epeint.iacr.org/2016/144 which presents a similar protocol with a security proof and integrated with shamir secret sharing.
Migration wou…