On 2019-04-25 00:51, Ludovic Courtès wrote:
Ludovic Courtès <[email protected]> skribis:
Another option would be to have an activation snippet that runs when
booting the newly installed system: if would check for a flag or
something (it could check for uninitialized passwords), and if it
determines it’s a first boot, open a dialog box asking for passwords.
We’d need to add a “post-install” service in the OS config that would do
just that.
That would be the most robust approach, but it’s also a bit more work I
guess. It’s also not so nice that users will see this extra service in
their config.
Thoughts?
To which Florian replied:
Why can’t the installer just chroot into the new system and call
passwd?
That makes a lot of sense, I feel silly for not thinking about it. :-)
(In fact, we don’t even have to chroot since we can directly use (gnu
build accounts) to write the shadow file in the right place.)
This is implemented by these commits:
91a7c4998f installer: Ask for the root account password.
898677ed17 installer: Ask for user password and initialize /etc/shadow.
I ran a full install and confirmed that it works as expected. You’re of
course welcome to try it out!
I realized later that I forgot to add a password confirmation box. I
guess we should add one, right?
Yes, that sounds like a good idea.
--
Cheers
Swedebugia
