It looks like my prediction is still on track.
bubble start between 25th sept. and 25th oct.
Now CCMF!
That seems to be a very (and even too quick rise to the top).. and where is the top gonna be in your enlightened vision? <-- look left. |
|
|
|
pretty sure google trends is lagging indicator
So, we are half way to the top already  SELL SELL SELL!! lol |
|
|
|
It looks like my prediction is still on track.
bubble start between 25th sept. and 25th oct.
Now CCMF!
Maybe this IS the bubble start? Yes it is  That's why I say it is on track. I also predict the top, hope I'm right. My trades are dependent on it.  Google trends has been a real time method that could have told you the last 3 bubbles were occuring. Currently showing an upswing in attention. Has increased the last 3 months http://www.google.com/trends/explore#q=%2Fm%2F05p0rrxI know, this is what I made earlier:  |
|
|
|
I just moved to pocket dice.
Approval is automatic, 0,001 btc/post for senior member.
If you like post alot, PocketDice can pay you more For Senior rate , max 100 posts total : BTC 0.1 per month meanwhile,if you like post lesser, CoinBroker is your choice Yes, but CoinBroker is closing, otherwise I would have stayed. Coinbroker will close on 21st october, so actually you still have 1 more week to stay if you want. I don't want to wait for all other participants searching for alternatives which makes the chance of approval to a new campaign more difficult. If you do the math, coinbroker's rate per post is higher than pocketdice
I know, but I post 25+ a week, then it's better to go for pocketdice. edit: but don't get me wrong. CoinBroker was excellent while it lasted. |
|
|
|
I just moved to pocket dice.
Approval is automatic, 0,001 btc/post for senior member.
If you like post alot, PocketDice can pay you more For Senior rate , max 100 posts total : BTC 0.1 per month meanwhile,if you like post lesser, CoinBroker is your choice Yes, but CoinBroker is closing, otherwise I would have stayed. |
|
|
|
It looks like my prediction is still on track.
bubble start between 25th sept. and 25th oct.
Now CCMF!
Maybe this IS the bubble start? Yes it is That's why I say it is on track. I also predict the top, hope I'm right. My trades are dependent on it. |
|
|
|
|
It looks like my prediction is still on track.
bubble start between 25th sept. and 25th oct.
Now CCMF!
|
|
|
|
|
I just moved to pocket dice.
Approval is automatic, 0,001 btc/post for senior member.
|
|
|
|
|
My previous coinbroker campaign ended so I joined the campaign and I'm waiting for approval.
It really looks professional.
|
|
|
|
Payment sent for this week, please do check.
Announcement to all members in this campaign:
Thanks for all your participation in this sig campaign; however, the campaign will close on next Tuesday(Oct 21st), please notice in advance.
Yes, thank you and good luck with your business. |
|
|
|
Wait, you're not a native English speaker?? Your English is much better than many (most?) native speakers I've seen on this board...
thnx Sorry, I actually don't know that much about JtR... but I think that the --wordlist option just takes the input file and uses each line as a single password, so nothing at all like btcrecover's token file. JtR can make all sorts of alterations to each line, but I don't know much about making JtR construct whole passwords the way btcrecover does.
They indeed work different. I'm now experimenting with both applications. You can however use both programs together: you can run btcrecover with the --listpass option (and with no --wallet), and it will generate and output whole passwords to test, one per line, and then you can use JtR (with it's better cracking speed) to actually try the passwords. I imagine there's a way for JtR to accept passwords directly from it's stdin, so you could pipe the output of btcrecover directly to JtR, e.g. btcrecover.py --token tokens.txt --listpass | john --options... Sounds like a great idea! Best of both worlds! I'm not in a hurry and I will experiment a bit with both. I keep you updated about the result. |
|
|
|
nobody can reset the password for you.
I was not asking for it, please read. If you cannot find the password, you will lost those coins.
Wrong. I was asking for brute forcing, there is a very good chance to get them back. there's a constant debate between online vs offline wallets ..
Not here. |
|
|
|
, I mean if you know that the password contains "house" and "tree" and 2 or 5 other characters/numbers. Is it still possible to bruteforce through all these options?
Like
housetree11111
housetree11112
housetree11113
Sure, here's a token file: That third token becomes all combinations of numeric digits, between 2 and 5 digits long, and can appear in the beginning, end, or between the other two tokens. It's described here in the tutorial: https://github.com/gurnec/btcrecover/blob/master/TUTORIAL.md#expanding-wildcardsIf you'd like to restrict that wildcard token to the end, you'd use this: That "$" forces it to be at the end (if present at all, it doesn't make the token required in every try). That feature is described here: https://github.com/gurnec/btcrecover/blob/master/TUTORIAL.md#anchorsWell, I should have read better! Since english is not my native language and there was a lot of text I did not read everything (yet) Also due to the fact I could not wait to begin testing  I'm trying to use a wordlist with JtR but I can't really get it to work. My hash file looks good, I extracted the hash from a blockchain.info wallet with the tool called blockchain2john. The password is something like house1tree2 I made a wordlist.txt But when I run john with: ./john --wordlist=../../wordlist.txt --rules ../../wallet.hash I get: Loaded 1 password hash (Blockchain, My Wallet [PBKDF2-SHA1 AES 4x SSE2])
Will run 2 OpenMP threads
Note: This format may emit false positives, so it will keep trying even after
finding a possible candidate.
Press 'q' or Ctrl-C to abort, almost any other key for status
0g 0:00:00:00 DONE (2014-10-09 23:13) 0g/s 536.6p/s 536.6c/s 536.6C/s Caring
Session completed
Then I do: ./john --show ../../wallet.hash and get: 0 password hashes cracked, 1 left What's wrong? All the words are in the wordslist. By the way, there is a small error in the code you gave earlier. python -c "import urllib2,json;f=urllib2.urlopen('https://blockchain.info/wallet/9bb4c672-563e-4806-9012-a3e8f86a0eca?format=json');print json.loads(f.read())['payload']" > wallet.json.aesshould be: python -c "import urllib2,json;f=urllib2.urlopen('https://blockchain.info/wallet/9bb4c672-563e-4806-9012-a3e8f86a0eca?format=json');print json.loads(f.read())['payload']" > wallet.aes.json(wallet extension changed from json.aes to aes.json) |
|
|
|
So I got this up and running and was able to crack a zip file which I encrypted with a simple password.
I was amazed to see how quick the password was cracked.
First I had to extract the password hash from the encrypted zip file and then I had to do "./john zip.hash"
But how do I extract the password hash from the "wallet.aes.json"?
edit: now downloading bleeding version, I saw something about blockchain2john, might be it.
Yup, that's the one. I don't know if you've finished compiling the bleeding version yet, Yes, it's already bruteforcing a "wallet.aes.json" file without wordlist. It seems to work, no success with the password yet (just testing on a slow laptop) but it might be worth getting an OpenCL or Cuda version compiled and working, it runs around 8ish times faster than the CPU-only version (and FYI CPU-only JtR runs about 6 times faster than btcrecover with Python 2.7.8+).
It seems that no special effort should be done to compile for OpenCL or Cuda. Am I right? The install file says: ./configure should find and enable any extra stuff you have, including OMP,
OpenCL, CUDA and extra libraries mentioned above. I also managed to have this tool up and running. I made myself a new blockchain wallet with a password like "house23tree1"
It took 30 seconds to crack the wallet. I made a token file with about 7 words and numbers.
Very nice tool if you know all contents of a password, but not exactly what came first and last.
As far as I can see I was not able to bruteforce any unknown characters. You really should put everything into the token file
What do you mean by "bruteforce any unknown characters"? Well, I mean if you know that the password contains "house" and "tree" and 2 or 5 other characters/numbers. Is it still possible to bruteforce through all these options? Like housetree11111 housetree11112 housetree11113 |
|
|
|
If the downloaded file doesn't start with these two characters: {" , and if you've created or modified (e.g. added new receiving addresses) to it at sometime after March, 2012 (when the wallet format changed again), and if you're on (or have easy access to) Linux and are comfortable compiling software, then I'd recommend John the Ripper ("bleeding-jumbo" version). It's faster than the alternative (and much faster with a GPU).
So I got this up and running and was able to crack a zip file which I encrypted with a simple password. I was amazed to see how quick the password was cracked. First I had to extract the password hash from the encrypted zip file and then I had to do "./john zip.hash" But how do I extract the password hash from the "wallet.aes.json"? edit: now downloading bleeding version, I saw something about blockchain2john, might be it. edit2: definitely it! I'm now trying to bruteforce his wallet I might try it first with my own test wallet and some tokens to see if it is really succesful I also managed to have this tool up and running. I made myself a new blockchain wallet with a password like "house23tree1" It took 30 seconds to crack the wallet. I made a token file with about 7 words and numbers. Very nice tool if you know all contents of a password, but not exactly what came first and last. As far as I can see I was not able to bruteforce any unknown characters. You really should put everything into the token file |
|
|
|
Ask side on Stamp looks flat as ball room floor. I can only imagine what happens if we really should see a bigger short squeeze! That train won't be able to stop anymore!!!
It's incoming in my opinion. When we touch 400 we'll see closing shorts popping like champagne bottles. Ad there will be people who will get hurt hard. Let it happen!  |
|
|
|
Amazing trains, all powered by bitcoin fusion.  |
|
|
|
I happened to come across this thread about an hour ago randomly and I think it might be perfect timing for you and your friend to get some help in a safe & secure way by a trusted member. Good luck to you guys I hope you are able to regain access to your wallet. Great find! I might consider using this service when I'm not able to bruteforce it myself. Thanks. |
|
|
|
Ready for the next bubble(s)!
You do realize that when everybody expects a bubble (like now), the chances of one actually happening are really slim? Yes! And that's why it's going to happen! There are only a few morons (me included) who expect the bubble to start right now. If i ask my colleagues, they are laughing at me when I urge them to buy some satoshis. Well, let me laugh to them in a few weeks. |
|
|
|
|
Gooooooooooood morning bitcointalk.
I love the smell of panic buying in the morning.
|
|
|
|
|
Show Posts
