similar to: samba 3.0.4 don't works with cracklib

Hi! before nothing, sorry for my english, I hope you understand me. I've a problem with the new samba 3.0.4-1.12, before I had the version 3.0.2a with LDAP for administrate all the users and when a samba password expired I used the "use cracklib" parameter for force the user to insert a strong password, well now this parameter isn't avaliable and I believe that must make it

-------- Original Message -------- Subject: password quality compliance Date: Fri, 14 Jan 2005 10:45:37 +0100 From: fandino <fandino@ng.fadesa.es> Reply-To: fandino@ng.fadesa.es To: samba@lists.samba.org Hello list, I'd like to have an advice about how to configure samba with password quality compliance. My file server is running samba 3.0.10 with a ldap backend and the users

I'm testing Samba 3.0.3pre2 and am particularly interested in the new --with-cracklib support. I see the configuration directive to enable cracklib functionality in the changelog, but am curious if anyone has any additional documentation. The man pages, etc... appear not to be updated yet. Is there any mechanism for 'tweaking' the password strenth rules, as there is with

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

Package: logcheck-database Severity: wishlist Tags: patch Please consider applying the attached patch. Logcheck doesn't match lines like the following right now: ---- Jan 26 04:26:29 space-based cracklib: updated dictionary (read/written words: ). ---- /Armin -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'),

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

Hello, I'm using samba 3.0.11 and SuSE Enterprise Server 8 (SLES8). All authentication tests using sambaclient works as expected, I can authenticate logon requests, but when I use windows 98 clients authentification fails with some password lenghts :-?. I know it sounds weird but I can reproduce it as many times as I want. i.e: password "aaa" -> smbclient - always works

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

seems to mess up the pam for swat. [root at host67 security]# rpm -qf /etc/pam.d/samba samba-3.0.25b-1.el4_6.4 [root at host67 security]# cat /etc/pam.d/samba #auth required /lib/security/pam_stack.so service=system-auth #account required /lib/security/pam_stack.so service=system-auth auth required pam_stack.so service=system-auth account required

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

[Mod: Other lists removed from the headers. The patch looks okay but I did not really checked it line by line -- alex] Last night I sent to redhat-list a letter with a patch. After sleeping a little I found that my patch is not enough correct. Now I post the new patch and description of the problem. In redhat distribution passwd program uses PAM, namely, pam_unix_passwd.so. This module use

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'm following the recipe 26.2.1.4 to disable roaming profiles for win9x and XPpro machines, but perhaps I'm missing something because it doesn't seem be possible get the home shares mapped with profiles disabled. windows machines fails with this error: ------------------------------------------------------------------- net use u: /HOME The user's home directory has not

Hi, maybe I didn't explained myself well. What i meant is that the user can't have the SID S-1-5-21-528226156-890416033-2029241632 but MUST have a sid like S-1-5-21-528226156-890416033-2029241632-xxxx ( where x is usually assigned automatically by the add user's script) Best Regards, Bruno Guerreiro -----Original Message----- From: Jos? M. Fandi?o [mailto:samba@fadesa.es] Sent:

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, I am using Centos 5.4 x86_64 with kernel 2.6.18-164.11.1.el5xen. I've installed a Centos 5.4 (64 bit too) DomU (paravirtualized), process was apparently with no problems, but DomU refuses to start, this the error: Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 498, in run_domain vm.startup() File

Hello friends, I'm having a problem with my home server (ASUS A7V133 motherboard) which has a horrible performance with ATA disks connected to an integrated promise controller. Below you can see iozone results of the same disk connected to the primary/ secondary controller versus the promise one. Promise ATA100 controller: ========================= Version 1.02a ------Sequential

I also sorted the list. Between libguestfs 1.28 and 1.30, the appliance grew from 95MB to 213MB. Using guestmount and filelight (see link below) I could see that the main contributor was these two directories, which should not be necessary. With this change, the size goes down to 119MB. See also: https://rwmj.wordpress.com/2015/07/23/why-has-the-libguestfs-appliance-grown-by-118-mb/ ---

Hi, Oliver. Maybe something like this (add this script to your crontab): ------------------------8<-------------------------- #!/bin/bash # # File: asterisk-watchdog.sh # Date: 2015.05.26 # Build: v1.0 # Brief: Secuencia para monitorizar procesos. # # ${PATH}: Variable de entorno con las rutas a los ejecutables. PATH=/bin:/sbin:/usr/bin:/usr/sbin # ${DAEMON}:

I would like to bump my question 2015-05-27 10:21 GMT+03:00 Krutskikh Ivan <stein.hak at gmail.com>: > Hmm, looks like it's not. I've just set the password for something that > cracklib-check would argue using both ad management tools and at windows > login. Should it work that way or I'm missing something? > > My dc's smb.conf: > > [global] >