Fixed.
Thank you John for your comment, which made me realize that crackcheck
was something I needed to compile myself. I had though this was perhaps
a version difference between older and newer versions of cracklib. In my
case I was using prebuilt RPM's. Please see my notes below for my steps
t;
> Thanks!!!
>
> mtoal
>
> ---- Original Message
> Subject: [Samba] samba password complexity help?
> Date: Thu, 17 Dec 2009 14:38:34 -0600
> From: Morgan Toal
> To: samba@lists.samba.org
>
> Hi there,
>
> Here are the facts:
> - I have samba 3
---
Subject: [Samba] samba password complexity help?
Date: Thu, 17 Dec 2009 14:38:34 -0600
From: Morgan Toal
To: samba@lists.samba.org
Hi there,
Here are the facts:
- I have samba 3.4.2-0.42.fc11 running on a Fedora 11 system.
- Samba is acting as a domain controller, no Windows server involve
Hi there,
Here are the facts:
- I have samba 3.4.2-0.42.fc11 running on a Fedora 11 system.
- Samba is acting as a domain controller, no Windows server involved.
- I am using tdbsam.
- I need to enforce certain password requirements.
The password requirements are:
- min 8 characters
- expiration
On Friday 31 July 2009 10:22:32 Radek wrote:
Hi Radek,
>
> I want to use crackcheck to check password complexity, but users (when
> password change failed because of complexity check fail) gets only
> information about valid password length, password history. I think that may
> be a problem for u
Hello,
I want to use crackcheck to check password complexity, but users (when
password change failed because of complexity check fail) gets only
information about valid password length, password history. I think that may
be a problem for users.
How can I (or Can I?) give them i
Hello,
I want to use crackcheck to check password complexity, but users (when
password change failed because of complexity check fail) gets only
information about valid password length, password history. I think that may
be a problem for users.
How can I (or Can I?) give them information a
I'm setting up password complexity requirements on our Samba server,
using the "check password script" option, the provided crackcheck.c
program, and the "min password length" account policy. Everything
works; however, the error message that a Windows client gets when a
new password fails to pass
Hello,
What's the best way to enforce password complexity on a samba PDC machine?
Do I use standard linux methods (and if I do will my users get a sensible
message when they try to get windows to change to an insecure password?) or
do I use group profiles to do it?
Cheers,
Chris.
--
To unsub
