he wanted to create them by porting from NT and by automation. This
incidentally would be a major step to making linux be adoptable in the
workplace large or small. Not everyone is going to want to try and sell
something to skeptical windows users that says 'password insecure' and
makes them type something in. That confuses people. That makes skeptical
people mock the new and the different. If you're in this guys position
you want it done and set up so nobody can complain. And there you are
offering command line manual input. And what if his company is small now,
it still rocks to have automation, because he might have to do this again
some day. Dude, put your linux desktop hat away (the red one) and put on
your intelligent systems admin hat. I think they are starting to make one
without daemon horns but I am not sure.
On Fri, 26 Jan 2001, marsden wrote:
> Date: Fri, 26 Jan 2001 14:45:51 -0800
> From: marsden <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED]
> Subject: Re: [expert] Password issues
>
> At 03:34 PM 1/26/01 -0600, you wrote:
> >This is a good point. I don't think Samba supports pam.d rejection of
> >passwords and since I'll be using password synchronization this is really
> >important. I guess I'll just have to live with weak passwords untill a
> >better solution comes my way.
> >Has anyone tried to do something like this?
>
> Sir
> How many passwords/users are you considering? You can set up users and
> their passwords via the commandline, and while Linux will complain, at
> least both RedHat and Mandrake 7.1 will allow you to *use* a silly
> password. Once you see "password authenticated" it has been setup,
> regardless of how easy it is to crack.
>
> Our company is small enough that we set up less than 1 user a month, so I
> simply input the info on the command line instead of using the gui provided
> by Mandrake.
>
> Anybody else have any brilliant ideas?
>
> But do, please, bug them to update their passwords.
>
> Marsden
>
>
