5 ms·
How to Share a Secret [pdf] (1979)
- nanomonkey 4y agoDark Crystal (https://darkcrystal.pw/ https://darkcrystal.pw/) provides a toolkit (a set of protocols, libraries and reference code) for using Shamir's Secret Sharing within different social fabrics.
- aabdelhafez 4y agohttps://github.com/incipher/shamir https://github.com/incipher/shamir Here's a CLI, written in Go, that uses HashiCorp Vault's implementation of the Shamir Secret Sharing algorithm and exposes its functionality to the command-line in an easy-to-use manner. I personally use it to divide my password manager's master password into shares that are given to family members and close friends in order for them to collectively reconstruct my master password and obtain access to my password vault in case I pass away. Disclaimer: I'm the author.
- lawrenceyan 4y agoNow they teach this to undergraduate students sophomore year.
- Wuzado 4y agoOriginal paper describing Shamir's Secret Sharing, (1979).
- deleted 4y ago[deleted]
- TeeMassive 4y agoThe article is very easy to read assuming some pre-calculus mathematical knowledge. Very intersting thank you.
- alberto_ol 4y agowikipedia article: https://en.wikipedia.org/wiki/Shamir%27s_Secret_Sharing https://en.wikipedia.org/wiki/Shamir%27s_Secret_Sharing
- janandonly 4y agoToday, this is one of the way's to split up Bitcoin Key's to distribute over multiple participants and/or locations.
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- y7 4y agoOne other thing that is really cool about secret sharing, is that you can actually perform computations (addition, multiplication) on secret-shared numbers. This way you can actually perform arbitrary calculations "in the encrypted domain", in a way that is currently a lot more practical than fully homomorphic encryption. See https://en.wikipedia.org/wiki/Secure_multi-party_computation https://en.wikipedia.org/wiki/Secure_multi-party_computation
- atulsnj 4y agoAre there any projects that have implemented this in production?
- jon-wood 4y agoHashicorp Vault by default makes use of this mechanism to ensure certain actions (most notably starting Vault and unlocking the secret store for use) require multiple users to approve it.
- alipitch 4y agoThanks. Going through the docs now. https://www.vaultproject.io/docs/concepts/seal#shamir-seals https://www.vaultproject.io/docs/concepts/seal#shamir-seals Shamir seals The default Vault config uses a Shamir seal. Instead of distributing the unseal key as a single key to an operator, Vault uses an algorithm known as Shamir's Secret Sharing to split the key into shards.
- pxc 4y agoMozilla SOPS, a tool for encrypting secrets for storage in source control systems, lets you encrypt secrets using the Shamir Sharing Threshold. You can use (and mix and match!) keys stored in of the first-party cloud secrets managers (AWS Secrets Manager, GCP KMS, Azure Key Vault), Hashicorp Vault, GnuPG, or Age. Various IaC ecosystems have integrations for it. It's probably the best way to store secrets for Nix-based deployments, and there are also docs and integrations that pair it up with Kubernetes and Terraform. Idk how many companies are really using keygroups, though. Probably in some of them, the repos are public and can tell you that. https://github.com/mozilla/sops https://github.com/mozilla/sops
- ggurgone 4y ago~12 years ago at university I used Shamir's Secret Sharing to implement a tool that enables written exams to be authenticated and yet anonymous. You can read a later publication from my professor here https://www.scitepress.org/Papers/2011/34814/34814.pdf https://www.scitepress.org/Papers/2011/34814/34814.pdf
- hn_throwaway_99 4y agoDoes anyone know if secret sharing, or the equivalent, is provided by cloud vendors as a way to secure extremely sensitive high level permissions? For example, most cloud services have the concept of an "owner" account that has full access to everything in a project. Most security advice I've read says that pretty much nobody should have access to the owner account - the credentials for the account should basically be locked in a vault (but that kinda just pushes the issue to "who has the keys to the vault"). Instead, what I'd like to do is share the owner account password into 4 parts, where any 2 are needed to get access to the owner account. That way no single employee can "go rogue" on their own. Obviously I can share the password by myself using something like SSS, but would be nice if I could just designate a group of n IAM accounts, but where a minimum of k are needed to get full owner privileges. The idea is similar to the "2 keys must be entered at the same time to launch the nukes" idea. Basically, just curious if other folks share their owner account creds that require some minimum consensus before accessing.
- gioazzi 4y agoI've been working on something similar to what you described[^1], using Shamir secret sharing to split the TOTP secret. Once enough key holders get together, a server generates some TOTP tokens, but only for a limited period of time. I wanted to use it in an enterprise environment to limit the access to AWS root users in a break-glass scenario. Now I no longer have such need and haven't developed it further, but the core features are there. As usual though with this kind of tools, any security problem becomes a key management problem and it'd need a bit more work to use it in the real world. [^1]: https://github.com/borgoat/farmfa https://github.com/borgoat/farmfa
- hn_throwaway_99 4y agoThanks, this actually helped give me a good idea about how I would like to do this now: 1. Generate the password for the owner account, store that in "standard" secrets storage where admins can access it. 2. Also require TOTP MFA for the owner account. Take the seed for the TOTP, and split that into N shares (where N is equal to the number of admins you want to share it out to) requiring K threshold (where K is the minimum number of admins that must come together), and give that out to your admins.
- nomoreusernames 4y ago
- erwincoumans 4y agoHere is a 68 line Python implementation to encrypt and decrypt: https://github.com/ergl/sss_py/blob/master/sss/shamir.py https://github.com/ergl/sss_py/blob/master/sss/shamir.py
- gnull 4y agoYou could extend the decoding procedure to tolerate errors. Shamir's secret sharing is the same thing as Reed-Solomon code, so you can reuse the error-correctimg property of the latter.
- itsmemattchung 4y ago> Eleven scientists are working on a secret project. They wish to lock up the documents in a cabinet so that the cabinet can be opened if and only if six or more of the scientists are present. What is the smallest number of locks needed? What is the smallest number of keys to the locks each scientist must carry? > it is not hard to show that the minimal solution uses 462 locks and 252 keys per scientist Probably obvious to most on HN but the answer didn't jump out at me immediately: 11! / 5!6! = 462
- water554 4y agoI wager this answer wasn’t obvious to most on HN…
- tromp 4y agoIt becomes obvious only after making the less than obvious assumption that locks can work in OR fashion rather than the usual AND fashion. How does one put 462 locks on a cabinet such that opening any one lock opens the cabinet?
- simongr3dal 4y agoYou could put several doors the cabinet. If using a chain, connecting locks in parallel between the links would be AND, and locks in series between the links would be OR.
- tromp 4y agoI've seen cabinets with multiple doors, and can even imagine them reaching the same space. But I've yet to see a cabinet lockable with a chain:-(
- Arrath 4y agoWhy, it simply requires the cabinet to be accessible all-around so you can fully wrap the chain, and a handle or the like to thread the chain through!