Author

Topic: Passphrase length (Read 192 times)

legendary
Activity: 2898
Merit: 1386
December 27, 2017, 01:45:30 PM
#9
Hi,

Still trying to figure out what TF happened to my passphrase. I didn't change it (checked that) and it's been the same for years but sometime between Nov 27 and Dec 5th it stopped accepting the passphrase.

On Dec 5 I found this in the debug -- it never appeared before. Is it possible the the wallet automatically assigned itself a new passphrase??

2017-12-05 13:02:17 Binding RPC on address ::1 port 8332 failed.
2017-12-05 13:02:17 HTTP: creating work queue of depth 16
2017-12-05 13:02:17 No rpcpassword set - using random cookie authentication
2017-12-05 13:02:17 Generated RPC authentication cookie C:\Users\USER\AppData\Roaming\Bitcoin\.cookie

Is there any way for me to find out the length of my passphrase? I've tried brute force (btc recover) using the passphrase I know but it's exhausting every possible combination. If I could know the length, it might help me create a more precise tokenlist.

I'm using Bitcoin version v0.14.2 , Win10

Anyone?


Sometimes keyboards can do funky things. Try a different keyboard?

Or type the password out and be sure it is what you think is right, then copy and paste it into the form.
legendary
Activity: 3416
Merit: 4658
December 26, 2017, 12:03:29 PM
#8
Does anyone know where/how I can find the length of a passphrase?

The actual length of the passphrase chosen is not stored anywhere.  The actual passphrase chosen is not stored anywhere.  Therefore, you are not going to be able to find out the length of the actual passphrase chosen without knowing what the passphrase is.

The allowable length of a passpharase in Bitcoin Core is much longer than you are likely to have chosen (Passphrases longer than 100,000 characters long are acceptable).  Therefore, knowing the maximum allowable length is not going to be helpful.
newbie
Activity: 13
Merit: 0
December 26, 2017, 11:50:05 AM
#7
Try to adjust the date of your pc back to when it was working and see if helps.

This is interesting. Why would that work?

Yes, did that as well. I haven't tried nearly as much combinations though. If I KNEW the length of the password, it would be most helpful. Does anyone know where/how I can find the length of a passphrase? Is it somewhere on the debug logs or any other file in the core files?
full member
Activity: 312
Merit: 111
December 26, 2017, 08:51:22 AM
#6
Try to adjust the date of your pc back to when it was working and see if helps.

This is interesting. Why would that work?



It did work before beside the dates mentioned, I have seen codes using date as a randomizer which is not a good practice but its worth of a try.
newbie
Activity: 13
Merit: 0
December 26, 2017, 08:11:13 AM
#5
Try to adjust the date of your pc back to when it was working and see if helps.

This is interesting. Why would that work?
legendary
Activity: 4060
Merit: 1303
December 26, 2017, 07:46:48 AM
#4
Hi,

Still trying to figure out what TF happened to my passphrase. I didn't change it (checked that) and it's been the same for years but sometime between Nov 27 and Dec 5th it stopped accepting the passphrase.

On Dec 5 I found this in the debug -- it never appeared before. Is it possible the the wallet automatically assigned itself a new passphrase??

2017-12-05 13:02:17 Binding RPC on address ::1 port 8332 failed.
2017-12-05 13:02:17 HTTP: creating work queue of depth 16
2017-12-05 13:02:17 No rpcpassword set - using random cookie authentication
2017-12-05 13:02:17 Generated RPC authentication cookie C:\Users\USER\AppData\Roaming\Bitcoin\.cookie

Is there any way for me to find out the length of my passphrase? I've tried brute force (btc recover) using the passphrase I know but it's exhausting every possible combination. If I could know the length, it might help me create a more precise tokenlist.

I'm using Bitcoin version v0.14.2 , Win10

Anyone?



Can you restore a backup from before November 27 and see if the phrase works with the backup?

newbie
Activity: 4
Merit: 0
December 26, 2017, 07:37:04 AM
#3
Try to use Electrum 1.8.1 and then export all private keys.
After that you should to create a new wallet and import your keys there.
full member
Activity: 312
Merit: 111
December 26, 2017, 06:55:50 AM
#2
Try to adjust the date of your pc back to when it was working and see if helps.
newbie
Activity: 13
Merit: 0
December 26, 2017, 04:16:30 AM
#1
Hi,

Still trying to figure out what TF happened to my passphrase. I didn't change it (checked that) and it's been the same for years but sometime between Nov 27 and Dec 5th it stopped accepting the passphrase.

On Dec 5 I found this in the debug -- it never appeared before. Is it possible the the wallet automatically assigned itself a new passphrase??

2017-12-05 13:02:17 Binding RPC on address ::1 port 8332 failed.
2017-12-05 13:02:17 HTTP: creating work queue of depth 16
2017-12-05 13:02:17 No rpcpassword set - using random cookie authentication
2017-12-05 13:02:17 Generated RPC authentication cookie C:\Users\USER\AppData\Roaming\Bitcoin\.cookie

Is there any way for me to find out the length of my passphrase? I've tried brute force (btc recover) using the passphrase I know but it's exhausting every possible combination. If I could know the length, it might help me create a more precise tokenlist.

I'm using Bitcoin version v0.14.2 , Win10

Anyone?

Jump to: