From 41e2482f1091466f6088075bd8d557afdc978352 Mon Sep 17 00:00:00 2001 From: bosch <55287964+Bosch-0@users.noreply.github.com> Date: Wed, 24 Nov 2021 11:56:50 +0800 Subject: [PATCH 1/4] Add Non-recommended schemes to PKM overview --- guide/private-key-management/overview.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/guide/private-key-management/overview.md b/guide/private-key-management/overview.md index 4a210f791..98ca0e0a7 100644 --- a/guide/private-key-management/overview.md +++ b/guide/private-key-management/overview.md @@ -127,6 +127,14 @@ The use cases for shared schemes include spouses managing a joint account, group - [Multi-key](/guide/private-key-management/multi-key/) - several keys and several people control the wallet +### Non-recommended schemes + +There are also several non-recommended private key schemes not detailed in this guide that are not widely used due to their poor security, lack of interoperability and unnecessary complexity. Below are schemes not recommended to be used in your Bitcoin applications and why. + +- Key sharding (Shamir's secret sharing): Sometimes referred to as an alternative to multi-key setups though the security risks are much greater. It's major drawbacks are a single point of failure, no key invalidation, no widely used implementation (though [SLIP-0039](https://github.com/satoshilabs/slips/blob/master/slip-0039.md) does exist), and poor auditability. Read more about the issues with key sharding [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/key-sharding-shamirs-secret-sharing). +- DAT files: A legacy form of backing up bitcoin private keys that use the generic .dat file type. These are are still used today by [Bitcoin Core](https://bitcoincore.org/) due to [security concerns](https://bitcoin.stackexchange.com/questions/92716/why-keys-generated-in-bitcoin-core-mismatch-that-from-online-generators-despite) with non-hardened key derivation. This form of private key scheme is not widely adopted due to it's lack of interoperability among wallets, not being human readable like a recovery phrase, and being potentially insecure if the user does not encrypt the keys contained within the file. +- 1-of-2 multi-key: This multi-key scheme may prevent users from misplacing a private key but offers no security benefits with added complexity to the scheme. Making multiple redundant copies of a single sig key offers the same benefits around key misplacement without the added complexity. Learn more [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/1-of-2). + --- Let's start by looking at the [automatic cloud backup](/guide/private-key-management/cloud-backup/) scheme. From ae54dc2a37dfecf5b59536d939a86a7479d7c290 Mon Sep 17 00:00:00 2001 From: bosch <55287964+Bosch-0@users.noreply.github.com> Date: Mon, 29 Nov 2021 13:36:51 +0800 Subject: [PATCH 2/4] Update guide/private-key-management/overview.md Co-authored-by: Christoph Ono --- guide/private-key-management/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/private-key-management/overview.md b/guide/private-key-management/overview.md index 98ca0e0a7..9d3dc961f 100644 --- a/guide/private-key-management/overview.md +++ b/guide/private-key-management/overview.md @@ -131,7 +131,7 @@ The use cases for shared schemes include spouses managing a joint account, group There are also several non-recommended private key schemes not detailed in this guide that are not widely used due to their poor security, lack of interoperability and unnecessary complexity. Below are schemes not recommended to be used in your Bitcoin applications and why. -- Key sharding (Shamir's secret sharing): Sometimes referred to as an alternative to multi-key setups though the security risks are much greater. It's major drawbacks are a single point of failure, no key invalidation, no widely used implementation (though [SLIP-0039](https://github.com/satoshilabs/slips/blob/master/slip-0039.md) does exist), and poor auditability. Read more about the issues with key sharding [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/key-sharding-shamirs-secret-sharing). +- Key sharding (Shamir's secret sharing): Sometimes referred to as an alternative to multi-key setups, but the security risks are much greater. It's major drawbacks are a single point of failure, no key invalidation, no widely used implementation (though [SLIP-0039](https://github.com/satoshilabs/slips/blob/master/slip-0039.md) does exist), and poor auditability. Read more about the issues with key sharding [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/key-sharding-shamirs-secret-sharing). - DAT files: A legacy form of backing up bitcoin private keys that use the generic .dat file type. These are are still used today by [Bitcoin Core](https://bitcoincore.org/) due to [security concerns](https://bitcoin.stackexchange.com/questions/92716/why-keys-generated-in-bitcoin-core-mismatch-that-from-online-generators-despite) with non-hardened key derivation. This form of private key scheme is not widely adopted due to it's lack of interoperability among wallets, not being human readable like a recovery phrase, and being potentially insecure if the user does not encrypt the keys contained within the file. - 1-of-2 multi-key: This multi-key scheme may prevent users from misplacing a private key but offers no security benefits with added complexity to the scheme. Making multiple redundant copies of a single sig key offers the same benefits around key misplacement without the added complexity. Learn more [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/1-of-2). From a4f3c6e6ba09306fb806f8d7cde6fdbb094be591 Mon Sep 17 00:00:00 2001 From: bosch <55287964+Bosch-0@users.noreply.github.com> Date: Tue, 30 Nov 2021 11:56:04 +0800 Subject: [PATCH 3/4] Update guide/private-key-management/overview.md Co-authored-by: Pavlenex --- guide/private-key-management/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/private-key-management/overview.md b/guide/private-key-management/overview.md index 9d3dc961f..e1e476ab8 100644 --- a/guide/private-key-management/overview.md +++ b/guide/private-key-management/overview.md @@ -131,7 +131,7 @@ The use cases for shared schemes include spouses managing a joint account, group There are also several non-recommended private key schemes not detailed in this guide that are not widely used due to their poor security, lack of interoperability and unnecessary complexity. Below are schemes not recommended to be used in your Bitcoin applications and why. -- Key sharding (Shamir's secret sharing): Sometimes referred to as an alternative to multi-key setups, but the security risks are much greater. It's major drawbacks are a single point of failure, no key invalidation, no widely used implementation (though [SLIP-0039](https://github.com/satoshilabs/slips/blob/master/slip-0039.md) does exist), and poor auditability. Read more about the issues with key sharding [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/key-sharding-shamirs-secret-sharing). +- Key sharding (Shamir's secret sharing): Sometimes referred to as an alternative to multi-key setups, but the security risks are much greater. Its major drawbacks are a single point of failure, no key invalidation, no widely used implementation (though [SLIP-0039](https://github.com/satoshilabs/slips/blob/master/slip-0039.md) does exist), and poor auditability. Read more about the issues with key sharding [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/key-sharding-shamirs-secret-sharing). - DAT files: A legacy form of backing up bitcoin private keys that use the generic .dat file type. These are are still used today by [Bitcoin Core](https://bitcoincore.org/) due to [security concerns](https://bitcoin.stackexchange.com/questions/92716/why-keys-generated-in-bitcoin-core-mismatch-that-from-online-generators-despite) with non-hardened key derivation. This form of private key scheme is not widely adopted due to it's lack of interoperability among wallets, not being human readable like a recovery phrase, and being potentially insecure if the user does not encrypt the keys contained within the file. - 1-of-2 multi-key: This multi-key scheme may prevent users from misplacing a private key but offers no security benefits with added complexity to the scheme. Making multiple redundant copies of a single sig key offers the same benefits around key misplacement without the added complexity. Learn more [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/1-of-2). From a64f5a75df35429eb28ca92159a5a81ee4a3244a Mon Sep 17 00:00:00 2001 From: bosch <55287964+Bosch-0@users.noreply.github.com> Date: Tue, 30 Nov 2021 11:56:10 +0800 Subject: [PATCH 4/4] Update guide/private-key-management/overview.md Co-authored-by: Pavlenex --- guide/private-key-management/overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/guide/private-key-management/overview.md b/guide/private-key-management/overview.md index e1e476ab8..25e10328d 100644 --- a/guide/private-key-management/overview.md +++ b/guide/private-key-management/overview.md @@ -132,7 +132,7 @@ The use cases for shared schemes include spouses managing a joint account, group There are also several non-recommended private key schemes not detailed in this guide that are not widely used due to their poor security, lack of interoperability and unnecessary complexity. Below are schemes not recommended to be used in your Bitcoin applications and why. - Key sharding (Shamir's secret sharing): Sometimes referred to as an alternative to multi-key setups, but the security risks are much greater. Its major drawbacks are a single point of failure, no key invalidation, no widely used implementation (though [SLIP-0039](https://github.com/satoshilabs/slips/blob/master/slip-0039.md) does exist), and poor auditability. Read more about the issues with key sharding [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/key-sharding-shamirs-secret-sharing). -- DAT files: A legacy form of backing up bitcoin private keys that use the generic .dat file type. These are are still used today by [Bitcoin Core](https://bitcoincore.org/) due to [security concerns](https://bitcoin.stackexchange.com/questions/92716/why-keys-generated-in-bitcoin-core-mismatch-that-from-online-generators-despite) with non-hardened key derivation. This form of private key scheme is not widely adopted due to it's lack of interoperability among wallets, not being human readable like a recovery phrase, and being potentially insecure if the user does not encrypt the keys contained within the file. +- DAT files: A legacy form of backing up Bitcoin private keys that use the generic .dat file type. These are still used today by [Bitcoin Core](https://bitcoincore.org/) due to [security concerns](https://bitcoin.stackexchange.com/questions/92716/why-keys-generated-in-bitcoin-core-mismatch-that-from-online-generators-despite) with non-hardened key derivation. This form of private key scheme is not widely adopted due to its lack of interoperability among wallets, not being human readable like a recovery phrase, and being potentially insecure if the user does not encrypt the keys contained within the file. - 1-of-2 multi-key: This multi-key scheme may prevent users from misplacing a private key but offers no security benefits with added complexity to the scheme. Making multiple redundant copies of a single sig key offers the same benefits around key misplacement without the added complexity. Learn more [here](https://docs.keys.casa/wealth-security-protocol/rejected-key-schemes/1-of-2). ---