>> (p.1)
    Author Topic: Making a brain wallet "cheat sheet"  (Read 3385 times)
    Topazan (OP)
    Sr. Member
    ****
    Offline Offline

    Activity: 354
    Merit: 250


    View Profile
    August 05, 2012, 06:23:58 AM
     #1

    To my understanding, using hashed string as a brain wallet carries with it the following risks:

    1. The passphrase might be forgotten.
    2. The passphrase might be randomly brute-forced by an attacker performing something like a dictionary attack on hashed strings.
    --2.5  There could be an unintentional collision with someone who happens to use the same passphrase.
    3. The passphrase might be stolen/phished/whatever.
    4.  Some combination of 3 and 2.  Part of the passphrase is stolen, and the rest is discovered through brute force.

    (1) is a big concern for me.  I intend to keep some savings in bitcoin for a long time, and it's very likely that I will forget the key if it is too difficult to remember.

    My idea is to make a list of personal questions, and have the answers be my passphrase.  I understand that because of (2) doing so is magnitudes less secure than using a randomly generated passphrase, but using a random phrase would make (1) likely.  I wanted to have the key based on facts that will remain relatively significant to me throughout my life.

    The list will be semi-secret.  I'm not going to show it in public, but I won't worry about keeping copies in several different places, online and offline.

    My thinking is that in order to access my BTC, the attacker would either have to know me very well or invest considerable resources researching me.  With a sufficiently long list, (2) is less likely, albeit still a possibility.  I was thinking at least fifteen questions.

    There's a small risk that the attacker will indeed know me well.  I need to think of some questions that I'll always remember the answer to, but have never told anyone else and never will.  This is easier said than done.

    To minimize the risk of someone finding the list and brute forcing the answers they don't know, I'll need to think of multiple questions with a large number of possible answers.  Any suggestions?  I've also included some "trick" questions, where the nature of the answer is unexpected.

    Comments?  Anyone with a better understanding of cryptography able to give me some idea of how many questions with how many possible answers would be needed to make this impractical to brute force?

    Save the last bitcoin for me!
Page 1
Viewing Page: 1