[wizard] 4-digit passcode code gets set incorrectly as "passphrase" on first run when flashing with --password

I haven't been able to reproduce, either with manually re-enabling the wizard (and making sure to empty my password with "sudo passwd -d phablet" before rebooting) or by flashing with --bootstrap. With image krillin/rtm 143.

How reliable is this bug for you?

This happens to me every time on mako, but maybe it's something that comes from the flash parameters:

ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --developer-mode --password=0000 --bootstrap

That could be the most likely explanation? I only use the --password because at one time ogra told people to use that. Maybe it sets the passphrase and the wizard simply doesn't change it?

Feel free to set this to Incomplete or whatever. I don't care if it only happens to me / developer mode users, I just wanted to be sure it doesn't happen on default configuration.

Confirming that bootstrap flashing without "--developer-mode --password=0000" does not have this issue. Feel free to mark this as Invalid, unless you want to fix the "CI mode" use case.

To be exact, when flashing with --developer-mode --password=0000, there is no selection given about which kind of security is used, but it does ask for the 4 digit code (twice). Ie it skips the screen one would select passphrase or passcode.

Nowadays the wizard lets you select the 4-digit pin code and set it, but it's actually still the passphrase set during flashing. For ease of use purposes, I now everytime go to system settings to really switch from 0000 passphrase to 0000 4-digit passcode manually.

Timo, looks like I never actually explained what's going on behind the scenes in this bug. There are two things going on in your workflow:

1) ubuntu-device-flash treats the --password argument as a passphrase always. Ideally it would inspect and see if it looks like a PIN, then set it as such.

2) The wizard can't override an existing password for the user. Ideally if a password was already set, those pages would be skipped or grayed out or something.

So that's two poor usability issues combining to be confusing when flashing with --password. But it's not a bug normal users see, just developers. I'd argue both could/should be fixed. But they just haven't been a priority.

Yep, certainly not a priority, just nice to have.