Comment 16 for bug 13497

I filed this bug originally, this one continues to cause a lot of people a lot
of grief.
I see in the comments suggestions of a quick fix or ugly solution.

My suggestion:
1) keep it simple, keep breezy-live as close as possible to breezy-install
2) the default user login should have a default password (possibly empty).
3) the default user login and password for breezy-live should be made well known
so as to not cause grief, consider modifying the popup window that asks for the
password to include default user login and password information.
4) breezy-live users should be able to change passwords, create users, install
openssh to allow for remote logins if desired. The user should be able to use
breezy-live in pretty much the same way as breezy-install and this includes the
ability to lock/unlock the screen.

Note: I presently have a lab computer with no hard drive running hoary-live with
an uptime of ~80 days, I have changed passwords, setup remote login with ssh and
can lock/unlock the screen on this machine. I move files around as needed to
other machines on the network, it works fine.