|
hashcat cmd line needed to brute force old lost wallet
|
07-23-2024, 03:12 AM
(07-23-2024, 03:08 AM)penguinkeeper Wrote: The bitcoin wallet algorithm is just simply very slow. Getting a better GPU would help and adding in the CPU may help a small fraction but it likely won't make a noticeable impact. The algorithm is simply slow, intentionally gotcha and what does the rule64 actually do, i saw it takes 65 days but without it takes 22 hours can you elaborate
07-23-2024, 03:22 AM
(07-23-2024, 03:12 AM)Luke10KxT Wrote:(07-23-2024, 03:08 AM)penguinkeeper Wrote: The bitcoin wallet algorithm is just simply very slow. Getting a better GPU would help and adding in the CPU may help a small fraction but it likely won't make a noticeable impact. The algorithm is simply slow, intentionally As I said earlier, it just makes new candidates based on variations of the passwords in the wordlist, so for example, "Penguin" could be turned into: penguin PENGUIN Penguin1 Penguin2024 etc and there would be 64 variations per password candidate, hence why it takes roughly 64x longer when you use rules, because it's 64x more passwords to try
07-23-2024, 03:55 AM
(07-23-2024, 03:22 AM)penguinkeeper Wrote:(07-23-2024, 03:12 AM)Luke10KxT Wrote:(07-23-2024, 03:08 AM)penguinkeeper Wrote: The bitcoin wallet algorithm is just simply very slow. Getting a better GPU would help and adding in the CPU may help a small fraction but it likely won't make a noticeable impact. The algorithm is simply slow, intentionally thank you so much for your valuable insight, do you know anbything about BTCRecover? trying to setup the btcrecover-tokens-auto.txt and a little stuck as to what to put as the attack letters or whatever at the biottom, this is what i currently have #--pause --wallet wallet.dat ########################################################################### # This is a comment, btcrecover ignores everything after a # sign # # To automatically load a tokenlist save it as btcrecover-tokens-auto.txt # # We can add arguments in the token by writing #-- only on the first line.# # # # Just copy this file and your wallet.dat in btcrecover-master folder # # Arguments are: --help, --wallet, --listpass and more # # All arguments can be found in btcrecover.py --help # # Run btcrecover without extra aguments (since they are in this file) # # so only write in CMD: C:\Python27\python btcrecover.py # ########################################################################### # Testing the Tokenlist # # Change #--help on line 1 of this file to #--listpass # # and run btcrecover.py # # # # Running the Brute-Force # # replace #--listpass above with: #--wallet wallet.dat # # # # You can never use --listpass and --wallet at the same time # # When using --listpass make sure you delete --wallet wallet.dat # # And if you use --wallet wallet.dat make sure you delete --listpass # # # ########################################################################### #----The most used wildcards, only use them to finetune the tokenlist!----# ########################################################################### # (space + # = #) (%S = $) (%% = %) (%^ = ^) (%s = 1 single space) # # The + sign = only try passwords with the following token in it. # # The ^ sign = try following token only in the begin of password # # %d = 1 digit(0-9) %2d = 2 digits(00-99) %1,3d = 1,2 or 3 digits (0-999) # # ^r1^ ^r2^ ^r3^ = Relative position of token # # The $ sign at the end of a token = token is at the end of password # # A space between tokens = OR # # (%a = a-z) (%A = A-Z) (%1,3in = 1,2 or 3 digits or a-Z) # # (%y = symbol !@#$) (%P = Anything) # ###########################################################################
07-23-2024, 11:39 AM
No and I wouldn't recommend using BTCRecover, Hashcat is significantly faster
07-23-2024, 01:56 PM
No, there is absolutely no guarantee that a hash will be cracked. If the password is weak, like "luke1" then it'll probably be cracked in seconds but if the password was strong, like "9eZE@,%Gp*59" then it'll never be cracked, in a million years. It just depends on the strength of the password
07-24-2024, 01:28 AM
(07-23-2024, 01:56 PM)penguinkeeper Wrote: No, there is absolutely no guarantee that a hash will be cracked. If the password is weak, like "luke1" then it'll probably be cracked in seconds but if the password was strong, like "9eZE@,%Gp*59" then it'll never be cracked, in a million years. It just depends on the strength of the password what do you think of this command line i came up with? hashcat -m 11300 -a 0 -o output_file.txt wallet.hash hashmob.net_2024-07-21.found -w 4 -O -d 1
07-24-2024, 01:43 AM
Yeah that's fine. Also, just to backup what I said earlier about how using both CPU and GPU is slower than just GPU alone, here are some hard numbers for you:
CPU + GPU: Code: --------------------------------------------------------------------GPU alone: Code: --------------------------------------------------------------------
07-24-2024, 01:48 AM
(07-24-2024, 01:43 AM)penguinkeeper Wrote: Yeah that's fine. Also, just to backup what I said earlier about how using both CPU and GPU is slower than just GPU alone, here are some hard numbers for you: so just take off the -d? how do i know if it not being used anymore
07-24-2024, 02:42 AM
(07-24-2024, 01:43 AM)penguinkeeper Wrote: Yeah that's fine. Also, just to backup what I said earlier about how using both CPU and GPU is slower than just GPU alone, here are some hard numbers for you: Also have you heard of this gui for Hashcat? https://github.com/s77rt/hashcat.launcher |
|
« Next Oldest | Next Newest »
|
