[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: ppolicy not verifying password length (not active !!)



Could you please share the steps with commands. This probably will help me.

Regards
Sam

Sent from my iPhone

On 6 Mar 2014, at 4:40 pm, Rodrigo Coutinho <Rodrigo.Coutinho@ifap.pt> wrote:

Hi again,
 
I did create another user, gave it the proper permissions via ACL, and it worked, the policy was enforced when I tried to change another user's password.
 
Still in shock though, that the root user can mess up the other users data.
 
 
Regards
 


De: saurabh ohri [mailto:sam_ohri@yahoo.co.in]
Enviada: quinta-feira, 6 de MarÃo de 2014 04:06
Para: Michael StrÃder; openldap-technical@openldap.org; Rodrigo Coutinho
Assunto: Re: ppolicy not verifying password length (not active !!)

I Also stuck in this issue. My password policy was not working on openldap 2.4.23 so someone suggested me to upgrade as this is the older version. So i upgraded it to 2.4.39 but struggling to get SSL work for openssl.

really shock to see that there is no proper document for the installation and configuration. 2.4.39 have to be configured from source and not rpm so facing hell lot of issue.
 
Regards
Sam


On Wednesday, 5 March 2014 8:31 PM, Michael StrÃder <michael@stroeder.com> wrote:
On Wed, 5 Mar 2014 11:33:51 +0000 Rodrigo Coutinho <Rodrigo.Coutinho@ifap.pt>
wrote
> Ok, thank you for the information, but I must confess that I am a bit
> shocked, as that implies I can have a directory full of non compliant
> passwords. 
>
> So, that begs the question: How do we prevent this ?  What is the
> normal/standard way ? 

Mantra to be repeated thousands of times:

Never use rootdn to bind.


> Should one create another user with administrative privileges and use it to
> change passwords when needed ?


Yes.

Ciao, Michael.






A transmissÃo de mensagens por e-mail nÃo à absolutamente segura ou livre de erros. A mensagem pode ser intercetada, alterada, perdida, destruÃda, chegar ao destinatÃrio com atraso, ou mesmo com vÃrus, nÃo obstante o IFAP utilizar software anti-vÃrus.
Esta mensagem, incluindo eventuais ficheiros anexos, pode conter informaÃÃo confidencial ou privilegiada e destina-se a uso exclusivo dos seus destinatÃrios. Se nÃo for o destinatÃrio pretendido, informamos que a recebeu por engano, pelo que, qualquer utilizaÃÃo, distribuiÃÃo, reencaminhamento ou outra forma de revelaÃÃo a terceiros, impressÃo ou cÃpia sÃo expressamente proibidos. Se recebeu esta mensagem por engano, por favor contacte imediatamente o remetente por e-mail, e apague de imediato a mensagem do seu sistema informÃtico.
O IFAP declina qualquer responsabilidade por erros ou omissÃes na presente mensagem e eventuais consequÃncias, que resultem das situaÃÃes referidas.