similar to: Password complexity

Hey folks, My 'check password script' seems to work well, but I have a question about the messages returned to the user. Currently, it prints an extremely verbose message, a-la: "The password supplied does not meet the minimum complexity requirements. Please select another password that meets all of the following criteria: is at least 8 characters; has not been used in the previous

On Thu, 21 Jun 2018 09:55:59 +0200 Marco Gaiarin via samba <samba at lists.samba.org> wrote: > > AFAI've understood 'samba-tool domain passwordsettings' set domain > password settings, while the GPO equivalent settings is for the client > (windows client and server os). > > Currently i've enabled password complexity checks server side: > > root at

Hi all, can someone give a working example for checking the password complexity in samba? I have tried the next one 1. Download and extract samba-3.4.15.tar.zg. Go to samba-3.4.15/examples/auth/crackcheck and compile crackcheck 2. Copy crackcheck binary to the /usr/bin/ 3. Check that the program working correctly # /usr/bin/crackcheck -d /usr/share/cracklib/pw_dict 123 ERR - it is too short #

Hi Samba folks, I had a couple questions about password complexity checking. To preface, in smb.conf, we set: check password script = /usr/local/sbin/crackcheck -d /usr/share/cracklib/pw_dict Also, if I understand correctly: /usr/local/sbin/crackcheck comes from samba source rpm package. maybe we need to compile it ourselves. /usr/share/cracklib/pw_dict* comes from cracklib-dicts rpm

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 about expected complexity. I'm almost sure that with NT PDC they would get information about

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 90 days - last 10 passwords may not be reused - not a dictionary word Per the Samba 3.2 FAQ, the

Hi everyone, I am using crackcheck to enforce password complexity requirements on my PDC.? Windows obeys these password requirements, but the dialog box that pops up doesn't display the correct information.? This posting describes the same issue: http://lists.samba.org/archive/samba/2007-May/131795.html However, I'm not trying to change the message completely -- I just want it to

Hello, I want to use crackcheck to check password complexity, but users (when password change failed) 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 about expected complexity. Crackcheck exits with error -4, and writes information to stderr, maybe can I use that and send it somehow to

Mandi! Rowland Penny via samba In chel di` si favelave... > It doesn't have to contain punctuation: Ahem, i've write 'punctuation' but i meant 'Non-alphanumeric characters'. Sorry. > So, as I am sure you can see, 'kaaPxvqEXW' only passes the first two. > It contains uppercase and lowercase, but neither numbers or punctuation. Exactly i supposed.

Hello, I have a Samba PDC on which I use the "check password script" option in smb.conf to enforce a specific password complexity policy when the XP user changes his password with Ctrl-Alt-Del. This works fine, but when the password does not comply with the password complexity policy, XP shows the following dialog box: "The password supplied does not meet the minimum complexity

I would like to understand how the "check password script" interacts with enabling/disabling password complexity checks. That is: if I configure     check password script = /usr/local/samba/sbin/crackcheck -d /var/cache/cracklib/cracklib_dict is this called *in addition* to the default complexity checking, or instead of it? And if I set     samba-tool domain passwordsettings set

On Fri, Aug 9, 2019 at 11:05 AM neonira Arinoem <neonira at gmail.com> wrote: > Won't it be better to have a convention that allows lowercase, dash, > underscore and dot as only valid characters for new package names and keep > the ancient format validation scheme for older package names? > Validation isn't the only thing we need to do wrt package names. we also need to

Hello, I would like to enforce some level of password complexity when users change their password. I have a Samba PDC running on Debian set to sync Unix passwords. I'm trying to get Samba to work with cracklib, but it isn't going well. Here is what I've tried: Installed libpam-cracklib, compiled examples/auth/crackcheck and copied the binary to /usr/local/sbin. I added the

On 2019-08-09 14:27, neonira Arinoem wrote: > I do not follow you Gabriel. Package name must not use digit numbers. > Tarbal will use them, taken from the DESCRIPTION file, version field. > > That's why I consider the weird case name you presented as irrelevant, > and > not to be considered. ggplot2 ? Numbers are allowed in package names right now. > Le ven. 9 ao?t

Hallo, we run a Redhat samba 3.5.4 PDC with openldap 2.4 as user/passwordbackend. The ldap also contains the posix information for the users to login to some web/mail/etc. servers. I'm faced with the task to implement a 'both worlds' compatible paswword sync process regarding complexity etc. For the posix account password we use a webfrontend, configure to use pam/cracklib checks

I'm trying to set up a new CentOS 4.2 desktop, and gdm refuses to start. It blanks the screen, displays the swirling blue circle mouse cursor that appears to be an hourglass equivalent, then drops back to the console window. It repeats this several times then displays the following error: The display server has been shut down about 6 times in the last 90 seconds, it is likely that something

Hi all, I'm quite new to all this, so please go easy on me if I don't quite seem to say the right things. (any advice is good advice) I have a 3.0.14a-debian samba install, with ldap auth using pam_unix (see smb.conf below) We want to implement a few password checks for complexity, so I have written a pretty basic script (see below) which definitely exits 0 on a good password

Hi people! I have a few problems with the password strength in Samba. I have a PDC with LDAP on Debian Stable, with a few packages from backports. The problem is that I can't find a way to enforce strenght to the passwords of the users. I can't define a policy to force things like: number of uppercase letters, number of downcase letters, number of numbers in the password, to check the

AFAI've understood 'samba-tool domain passwordsettings' set domain password settings, while the GPO equivalent settings is for the client (windows client and server os). Currently i've enabled password complexity checks server side: root at vdcsv1:~# samba-tool domain passwordsettings show Password informations for domain 'DC=ad,DC=fvg,DC=lnf,DC=it' Password

I do not follow you Gabriel. Package name must not use digit numbers. Tarbal will use them, taken from the DESCRIPTION file, version field. That's why I consider the weird case name you presented as irrelevant, and not to be considered. Le ven. 9 ao?t 2019 ? 20:41, Gabriel Becker <gabembecker at gmail.com> a ?crit : > > > On Fri, Aug 9, 2019 at 11:05 AM neonira Arinoem