you misunderstood him. password=`echo $password | sha256sum` this pipes the password to sha256sum and adds \n at the end, so yes u have to put \n at the end when brute forcing. Oh I see - sorry about that - that was an unintended extra complication.
|
|
|
As the password was put onto the clipboard (at the end of the script) and then later "pasted" into the password prompt from GPG the LF is not actually *in* the actual hash that was used.
|
|
|
Am very appreciative of the effort being put into this and am guessing that unless there is a hacker with a lot of free computing power it will be very much a case of luck with the "riddle" at this stage (and as promised the next hint won't really make much difference).
|
|
|
Why not? You stated before you wouldn't empty the address until Jan 3rd. It takes time to figure out best ways to approach this and then implement. If you are attempting to evaluate the security model it seems counter-productive to cop out by reducing the difficulty too soon.
...I'd hate to spend too much effort and then just have you void it all by giving it away or closing the challenge....
Okay - assuming others feel the same then I won't make the next clue as revealing as I was going to (and any clue after that will not be released until the new year).
|
|
|
Thinking about the year that just ended, I cannot be thankful enough to be apart a part of a community that does not discriminate, does not hate (besides for the trolls), and does not care where you came from, who you are or your background. All of us work 24/7, with our blood, sweat, and tears to make this world a better place, a place where Bitcoin prevails!
FTFY - agree with the sentiments. I think 2013 is going to be an exciting time for Bitcoiners!
|
|
|
Interesting puzzle. "(at least)" isn't giving me any great ideas tho.
Well the next hint (if it's still unclaimed after 100 confirmations) should make it dramatically easier (as I am not going to let this drag out for too long).
|
|
|
sry didnt read the full post (in a hurry).
No worries at all - now > 60 confirmations and funds are still seemingly safe. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
I used "vanitygen" to create the address so am pretty certain that the encrypted content would start with:
Privkey:5
so password is in the following format? if so u should have told us earlier, we'r all searching for a real privkey. I was answering a question about what the *decrypted content* of the GPG message looks like (not about the "salt" formatting - only the "hints" that I give out are directly about that).
|
|
|
I used "vanitygen" to create the address so am pretty certain that the encrypted content would start with:
Privkey:5
|
|
|
will there be a 3rd hint?
If the funds are still there after 100 confirmations I will give a 3rd hint (and a 4th hint is probably not going to be necessary). ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
All the GPG options I used were default values (only filled in a name and email address and of course the password).
|
|
|
Okay > 50 confirmations now - second hint (which is actually a slightly different version of the first hint):
|
|
|
I used a Puppy distro on an old IBM Thinkpad X40 (am hoping to get a SUSE Studio distro that will work on it so I can share it but no luck getting that to boot so far).
I also have tested the exact same script on an OpenSUSE 12.2 install (running on 64 bit hardware).
|
|
|
Second hint will be coming after 50 confirmations...
|
|
|
Okay - I have 10 confirmations now and the BTC has not moved - so here is the first hint in regards to the line of the script that was changed: more hints to follow if the 10 BTC is not taken by the time I get up tomorrow. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
I finally managed to shut it up! ![Cheesy](https://bitcointalk.org/Smileys/default/cheesy.gif) I'm now just checking the dictionary! Good stuff - first clue is coming soon (am getting tired)...
|
|
|
I have made a 1 Gb dictionary but I cant tell gpg to shut up and just check the passphrase ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) it slows the whole process down Sorry am not an expert with GPG myself - but it does have a lot of options that you can't see from just the --help (try searching about that).
|
|
|
Looks like 8 confirmations now - getting late here (it's midnight in Beijing) but first hint will be posted before I go to bed.
|
|
|
Fundamental thinking can solve chickens FU/|/d@m3/\|t@l t|-|i/|/g C@/|/ $0lv3 <|-|icK3ns FUCK is the password (the only capitolised letters)
Sure - at least I think you have got the point then. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
I think that at least you were lucky that if this is a bug then you found a very honorable forum member to have found it with. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|