[Date Prev][Date Next]
Re: schema definition precedence
Today at 3:00pm, Dave Horsfall wrote:
> Never, ever, change a standard definition.
As a general rule that's nice. As a practical matter there are gastly
mistakes (such as facsimileTelephoneNumber, which doesn't provide ANY
search capability) which require correction to be usable.
Another example is uid, which is a security hole the size of Texas --
allowing substring matches so spammers can grab all your addresses! If
you want to use uid (and not have to redefine [like I am about to] every
objectClass that uses uid), you HAVE to modify it to remove substring
searches or you become a spam magnet.
Just my two cents (it's worth exactly what you paid for it)
Frank Swasey | http://www.uvm.edu/~fcs
Systems Programmer | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
=== God Bless Us All ===