BenWestgate
commented
1 year ago The check for Persistent Storage passphrase strength uses zxcvbn and indeed <50 bits is the cut off I tell users who already have a persistent storage to create a new one at.
The check for creating a seed backup passphrase or wallet spending passphrase is just that it is 12 characters, although I may eventually add an entropy requirement as well.
Would you like bails-wallet to require 50-bits of entropy on wallet passphrases or seed backup passphrases?
The only way you got into this situation is because you did not use a recommended passphrase when you set up Persistent Storage.
When you make a backup, it lets you set a passphrase for the new clone, so you're absolutely able to recover from this issue.
Can you tell me how you got shown this message?
print("")' 2>/dev/null)"
if [ -z "$existing_passphrase" ]; then
zenity --error --title="Error" --text="Existing Persistent Storage passphrase is required. Please provide the passphrase." $ICON
else
# Estimate passphrase entropy to see if we can proceed
entropy=$(keepassxc-cli estimate "${existing_passphrase// /}" | cut -f2 | tr -C -d '[:digit:]')
if ((entropy >= 65000)); then
break
elif ((entropy > 50000)); then
zenity --question --icon-name=dialog-warning --title='Warning: Weak Passphrase Detected' \
--text="Your passphrase is too weak..." \
--width=600 $ICON --ok-label='Continue' --default-cancel --cancel-label='Restart Now' && break || exit 1
else
zenity --warning --title='WARNING: Weak Passphrase Detected' \
--text="Your passphrase is too weak...." \
--width=600 $ICON --ok-label='Restart Now'
exit 1I use a passphrase of 'a' all the time in testing and have never seen it.
It's supposed to only show up when you have an existing Persistent Storage and not BAILS and try to install Bails to it. It won't let you if your Persistent Storage passphrase is weak.
extrapockets
I had a weak password for my Tail persistent storage, yet BAILS allowed me to make multiple wallets using that weak password as a passphrase (Keepassxc says it's < 40 bits entropy). Recently, upon restoring a wallet, my passphrase (identical to my weak Tails pw) failed the entropy check in Bails/bin/persistent-setup:
I don't know why I was allowed to create the wallet with the weak passphrase in the first place. One wallet was created three weeks ago, and another with the same weak passphrase was created two days ago. Now I've been funneled to the warning that I MUST delete my persistent storage and start over. I am planning to clone BAILS to avoid another long sync process, but this would be a discouraging situation for a user to find themselves in.