Michael DeHaan wrote:
> Dustin Black wrote:
>
>> How about simply generating a random password at RPM installation
time, and noting strongly in the comments of the default kickstart
files that it is so?
>>
>>
>
> The issue I have is that I don't think all of our users are clueful
> enough on how to replace the password hash.
>
Slight reading comprehension error on my part. Yes, this is doable, but
we still need a way to retrieve what the password used was, which gets
complicated. It also leaves the user without a way to log in on a
"stock" install.
I spend a lot of time doing IRC support, so solutions that are obvious
out of the box are preferred, so we don't have to keep answering the "I
can't log in" problem. So this may involve a more complicated solution,
and at that point, perhaps it's best solved by site-specific
policy/plans.
Shipping a snippet to create a random password is reasonable and
probably a good thing to do -- enabling it by default, not so sure.
IMHO: enabling by default is not a good idea so I'm with Michael. The snippet approach
suits my environment just fine.
/marcel
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It
may contain proprietary material, confidential information and/or be subject to legal
privilege. It should not be copied, disclosed to, retained or used by, any other party. If
you are not an intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.