-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Can anyone point me to a means of performing some sort of data validation on input data at the server end?
Specifically, I want to store email addresses to be looked up by sendmail when doing alias processing. I want to have these aliases managed by users who may not be totally trustworthy, so I'd like to knock out any attempts to add aliases that have redirection or pipe operators in them.
The printable string schema syntax (OID=1.3.6.1.4.1.1466.115.121.1.44) is pretty close to what I need, but it doesn't include the '@' character.
Any ideas?
Thanks in advance, Bob.....
On 12.03.2013 02:32, Bob Schorer wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Can anyone point me to a means of performing some sort of data validation on input data at the server end?
Specifically, I want to store email addresses to be looked up by sendmail when doing alias processing. I want to have these aliases managed by users who may not be totally trustworthy, so I'd like to knock out any attempts to add aliases that have redirection or pipe operators in them.
The printable string schema syntax (OID=1.3.6.1.4.1.1466.115.121.1.44) is pretty close to what I need, but it doesn't include the '@' character.
Any ideas?
Thanks in advance, Bob.....
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (MingW32) Comment: No comment
iD8DBQFRPneLpjfLzfdVw6YRAjueAKCV7fVyve4m0wTNy0S4/FNMrdT2XACcCryX Sn7CpG8ZHVVlUn+mu9kLE00= =nql5 -----END PGP SIGNATURE-----
Hi,
take a look at slapo-constraint(5). See the Admin Guide [1] for the short version.
Regards, Christian Manal
[1] http://www.openldap.org/doc/admin24/overlays.html#Constraints
openldap-technical@openldap.org
-
bob＠swin.edu.au -
Christian Manal