Wallet Phasephrase issue?

[uncle_muddy]

OK so been in the process of creating a couple of “cold storage” wallets to chuck some of this FTC that I have mined, and in doing so I think I have found a problem…

All of this has been carried out in a virtual environment, disconnected from any network, but I don’t think that is causing the issue I’m having.

When you come to import your private key, you need your wallet to be unlocked (this step is missing from the guide) so the following command needs to be entered into the console

[code]walletpassphrase 1000[/code]

As far as I can work out “1000” is the number of seconds you want your wallet to remain unlocked?

So I issue the command and get the following error

[quote]Error: The wallet passphrase entered was incorrect. (code -14)[/quote]

I think “know it’s not! I know what my password is” so I go to create a new address and I get promoted for my passphrase as you would expect, I enter exactly the same pass phrase, and the address is created!!So to make sure I’m not losing the plot completely I type the passphrase into a text editor, and copy it into memory. I go and create another address and just paste in my passphrase, again address created no problem.

So back to the console enter command from above pang paste, check it is what it says it is as you can see the charters in the console, and yes it’s correct. Returns

[quote]Error: The wallet passphrase entered was incorrect. (code -14)[/quote]

Arrgghh whats going on?

So I look at my phassphrase, it’s nothing to special but I did make it complicated even thou I was just messing around on a test system to make sure I could get everything working before transferring my FTC into the black hole of the block chain never to be seen again.

It turns out that thru the command line if your passphrase has “/” or “\” something goes a little wonky and it comes back with the above error!

UM

[A Former User]

Just enter is as: walletpassphrase youpassphrase 1000

Dont need these <>

[wrapper]

Just gonna say, they should have worked, hope you did put the <> in by mistake, otherwise it was an software bug issue.

>>>>>>>>>>>>>>>

Password Strength

Brute-force password cracking has come a long way. A password including capitals, numbers, and special characters with a length of 8 characters can be trivially solved now (using appropriate hardware). The recommended length is at least 12 characters long. You can also use a multi-word password and there are techniques to increase the strength of your passwords without sacrificing usability. The Usability of Passwords

However, simply using dictionary words is also insecure as it opens you up to a dictionary attack. If you use dictionary words, be sure to include random symbols and numbers in the mix as well.

If you use keyfiles in addition to a password, it is unlikely that your encrypted file can ever be cracked using brute-force methods, even when even a 12 character password might be too short.

Assume that any encrypted files you store online (eg. Gmail, Dropbox) will be stored somewhere forever and can never be erased.
Choosing A Strong Password

Make sure you pick at least one character in each group:

Lowercase: abcdefghijklmnopqrstuvwxyz
Uppercase: ABCDEFGHIJKLMNOPQRSTUVWXYZ
Number: 1234567890
Symbol: `~!@#$%^&*()-_=+\|[{]};:'",/? (space)

09 char = insecure
10 char = low security
11 char = medium security
12 char = good security (good enough for your wallet)
13 char = very good, enough for anything.

[uncle_muddy]

[quote name=“wrapper” post=“57994” timestamp=“1391901232”]
Just gonna say, they should have worked, hope you did put the <> in by mistake, otherwise it was an software bug issue.
[/quote]
Sorry to say kids I did not include <> in the command when I typed it into the command line. My phase phrase is 62 characters long and contains at least 10 symbols, and the rest is assorted junk from the list of

Lowercase: abcdefghijklmnopqrstuvwxyz
Uppercase: ABCDEFGHIJKLMNOPQRSTUVWXYZ
Number: 1234567890

So I’m thinking software bug here guys, easy enough to test. Install new client (not on the same computer) encrypt wallet with a simple password of /1234ABcd and then tray and issue a new address, when prompted enter the password, it works right? No try and do it form the command line

***EDIT*** Just thought I did not try a phrase with only / or \ in it so it maybe only one of the symbols that causes the issue!

UM