sean finney wrote:
hey,
On Tue, Jun 28, 2005 at 10:07:05PM +0200, Olaf van der Spek wrote:
or better, what if we prompt for the root password via debconf, and then
if the answer is non-blank, set the password? this wouldn't be very
hard to do.
The disadvantage would be another question.
As I prefer random passwords, I'd vote against it. :)
I'm not sure what kind of passwords others prefer, but I guess a
question is reasonable.
the problem with random passwords is that you have to somehow give them
to the admin, and i don't think policy will allow us to dump an
arbitrary file in /root (it would have to be a config file in /etc or
I guess it's also not safe to email the pass to root.
somewhere in /var). also, if we generated a random password for
root and the user missed the info, they'd probably be frustrated for a
bit before finding in a README.debian the information about what/where their
password is.
wrt debconf, the priority could be set to medium, so those who want to
avoid the question can do so.
How would you pass the random pass to the user in the case they supplied
no pass as answer to the question?
also, now that i think about it, we could put something in the postinst
that checks if it could connect to the mysql server w/o a password after
starting the server, and if so prompts the admin whether with an
ignore-and-continue/get-password/random-password choice of higher priority.
christian: what do you think of this?
sean
--
Olaf van der Spek
http://xccu.sf.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
