Bitcoin Forum
June 22, 2024, 08:24:31 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Breaking up a private key into pieces  (Read 1377 times)
daviducsb (OP)
Full Member
***
Offline Offline

Activity: 155
Merit: 100


View Profile
November 10, 2013, 06:29:06 AM
 #1

I have a Q for some of the cryptography connoisseurs out there.

If I break my private key into two and give each half to a relative, could a hypothetical thief hack into the rest of my private key by finding one of the two halves?

How much of a private key would one have to have access to in order to hack?

What if I lobbed off the first five and last five digits? Could someone who found the bulk of the key hack it?

I should know this by now but never enquired. Any help appreciated. Thx
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1079


Gerald Davis


View Profile
November 10, 2013, 06:32:57 AM
Last edit: November 10, 2013, 07:03:40 AM by DeathAndTaxes
 #2

If you cut a key with a key strength of 2^n in half then the key strength of either portion (assumed the attacker acquires the other portion) is reduced to in half to 2^(n/2).   An attacker would be 2^(n/2) times easier.

For 256 bit EDSA the full key has 128 bit strength security a half key then only has 64 bit strength if the attacker has the other portion.  While it may take some time and effort that is computationally feasible.  64 bit key strength should not be considered safe from brute force attack.  You have made the attackers job 2^64 = 18,446,744,073,709,551,616 easier. 

A much better option would be to XOR two 256 bit "partial keys" to create the final key.  Each partial key retains the full key strength.

ozgur
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
November 10, 2013, 06:49:14 AM
 #3

If you cut a key in half then the key strength of brute forcing the other half is reduced by half.

EDSA 256 bit keys has 128 bit strength security.

So if you cut it into two 128 bit "half keys" and the attacker has one it is only 64 bit key strength to resist an attack.  While it may take some time and effort that is computationally feasible.

A much better option would be to construct the partial keys using XOR making each key have full strength.

I know what you mean, but to make it clear;

it is not halved, it is 2^128 times easier Smiley
DeathAndTaxes
Donator
Legendary
*
Offline Offline

Activity: 1218
Merit: 1079


Gerald Davis


View Profile
November 10, 2013, 06:51:59 AM
 #4

If you cut a key in half then the key strength of brute forcing the other half is reduced by half.

EDSA 256 bit keys has 128 bit strength security.

So if you cut it into two 128 bit "half keys" and the attacker has one it is only 64 bit key strength to resist an attack.  While it may take some time and effort that is computationally feasible.

A much better option would be to construct the partial keys using XOR making each key have full strength.

I know what you mean, but to make it clear;

it is not halved, it is 2^128 2^64 times easier Smiley


I updated the post, your right it is unclear.  A clarification though, 256 bit ECDSA only has 128 bit key strength so half the key would be 64 bit key strength (too weak for me to sleep well at night).

So it is 2^64 (or a whole hell of a lot) easier to break then the full key.

Still you are dead on with the larger point.  It SIGNIFICANTLY degrades the strength of the key and 64 bit is too close for comfort in my book.   Keys with 64 bit key strength have been broken in a distributed computing project as a demonstration.  It is almost certain that major nation states have the ability to break keys with 64 bit strength in a reasonable amount of time.
J35st3r
Full Member
***
Offline Offline

Activity: 196
Merit: 100



View Profile
November 10, 2013, 09:45:40 AM
 #5

Depending on what you want to do with this, you could consider Shamir's secret sharing. It does rely on third party software, but there is an open source thread at https://bitcointalk.org/index.php?topic=142875.0 and also some discussion at https://bitcointalk.org/index.php?topic=148809.0

1Jest66T6Jw1gSVpvYpYLXR6qgnch6QYU1 NumberOfTheBeast ... go on, give it a try Grin
Abdussamad
Legendary
*
Offline Offline

Activity: 3640
Merit: 1571



View Profile
November 10, 2013, 10:03:23 AM
 #6

Another option is to do it in the native bitcoin way and create a multi signature address:

https://people.xiph.org/~greg/escrowexample.txt

Then give each relative one private key.

Yet another option is to use Armory for this. Armory can create m of n backups but, I believe, only via the command line. Search the forum for that thread.
daviducsb (OP)
Full Member
***
Offline Offline

Activity: 155
Merit: 100


View Profile
November 10, 2013, 07:26:09 PM
 #7

thanks all for the very solid info.  I will print this thread out to slowly reference

deepceleron
Legendary
*
Offline Offline

Activity: 1512
Merit: 1032



View Profile WWW
November 10, 2013, 08:21:57 PM
 #8

http://mywiki.wooledge.org/XyProblem
Ecurb123
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile
November 11, 2013, 09:46:42 PM
 #9

If you cut a key with a key strength of 2^n in half then the key strength of either portion (assumed the attacker acquires the other portion) is reduced to in half to 2^(n/2).   An attacker would be 2^(n/2) times easier.

For 256 bit EDSA the full key has 128 bit strength security a half key then only has 64 bit strength if the attacker has the other portion.  While it may take some time and effort that is computationally feasible.  64 bit key strength should not be considered safe from brute force attack.  You have made the attackers job 2^64 = 18,446,744,073,709,551,616 easier. 

A much better option would be to XOR two 256 bit "partial keys" to create the final key.  Each partial key retains the full key strength.



thanks to the OP for the question I was thinking about it too, and thanks to DeathAndTaxes for the explanation.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!