--=_33747e76bfe2c1fb040150770642610c Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8
Hi, I have released a new version of ppm: password policy module version 1.1 http://62.210.236.82/incoming/ppm-1.1.tar.gz The goal was to : - make the code more modular, - make the configuration file simpler, - simplify the configuration data structure To answer your question : > how do you distinguish a new class name from an existing reserved keyword? In version 1.0 : you can't, because everything is defining a class by default. But in fact, the need to have many class is not very common... In version 1.1 : class parameters begin by the keyword "class-". Furthermore, a regex table of allowed parameters is available. Thanks in advance for your interrest. David Le 2014-04-10 10:57, Howard Chu a écrit : > [email protected] wrote: > >> Full_Name: David Coutadeur Version: 2.4.39 OS: Debian wheezy 64 URL: >> http://62.210.236.82/incoming/ppm-1.0.tar.gz [1] Submission from: (NULL) >> (92.103.166.6) Hi, I am proposing this module extending password policy for >> integration into contrib/slapd-modules. (see URL attached) I get inspired by >> the ltb check password module, but I finally rewrote everything from scratch >> to better include new functionnalities. You can consider this as a >> replacement for ITS Incoming/7412 The code has been tested a little, and a >> work has been done to make the code cleaner, but do not hesitate for any >> suggestion or remark. > > I took a brief look at it. The config file syntax seems a bit awkward, how do > you distinguish a new class name from an existing reserved keyword? > > I'd like to hear other people's opinion on the actual checks being performed. > >> David Links: ------ [1] http://62.210.236.82/incoming/ppm-1.0.tar.gz --=_33747e76bfe2c1fb040150770642610c Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=UTF-8 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> <html><body style=3D'font-size: 10pt; font-family: Verdana,Geneva,sans-seri= f'> <p> </p> <p>Hi,</p> <p>I have released a new version of ppm: password policy module version 1= =2E1</p> <p>http://62.210.236.82/incoming/ppm-1.1.tar.gz</p> <p>The goal was to :</p> <p>- make the code more modular,</p> <p>- make the configuration file simpler,</p> <p>- simplify the configuration data structure</p> <p> </p> <p>To answer your question :</p> <pre>> how do you distinguish a new class name from an existing reserved= keyword?<br /><br />In version 1.0 : you can't, because everything is defi= ning a class by default. But in fact, the need to have many class is not ve= ry common...<br />In version 1.1 : class parameters begin by the keyword "c= lass-". Furthermore, a regex table of allowed parameters is available.<br /= ><br /><br />Thanks in advance for your interrest.<br /><br />David<br /><b= r /></pre> <p>Le 2014-04-10 10:57, Howard Chu a écrit :</p> <blockquote type=3D"cite" style=3D"padding-left:5px; border-left:#1010ff 2p= x solid; margin-left:5px"><!-- html ignored --><!-- head ignored --><!-- me= ta ignored --> <pre><a href=3D"mailto:[email protected]";>[email protected]</a>= wrote:</pre> <blockquote type=3D"cite" style=3D"padding-left:5px; border-left:#1010ff 2p= x solid; margin-left:5px">Full_Name: David Coutadeur Version: 2.4.39 OS: De= bian wheezy 64 URL: <a href=3D"http://62.210.236.82/incoming/ppm-1.0.tar.gz= ">http://62.210.236.82/incoming/ppm-1.0.tar.gz</a> Submission from: (NULL) = (92.103.166.6) Hi, I am proposing this module extending password policy for= integration into contrib/slapd-modules. (see URL attached) I get inspired = by the ltb check password module, but I finally rewrote everything from scr= atch to better include new functionnalities. You can consider this as a rep= lacement for ITS Incoming/7412 The code has been tested a little, and a wor= k has been done to make the code cleaner, but do not hesitate for any sugge= stion or remark.</blockquote> <pre>I took a brief look at it. The config file syntax seems a bit awkward,= how do you distinguish a new class name from an existing reserved keyword? I'd like to hear other people's opinion on the actual checks being performe= d.</pre> <blockquote type=3D"cite" style=3D"padding-left:5px; border-left:#1010ff 2p= x solid; margin-left:5px">David</blockquote> </blockquote> <p> </p> <div> </div> </body></html> --=_33747e76bfe2c1fb040150770642610c--
