Vincent, can you remove the Security Sensitive Bug check?  It is preventing me from checking into CVS.

Seems that Huzaifa already did that, so you should be ok now.

Hi, 

I am testing this bug to verify the fix.
I have 389, 1.2.8 and executed below steps :


1) You have to have a client capable of sending an empty modify request -
mozldap ldapmodify will not let you do this, but openldap ldapmodify will:

# /usr/bin/ldapmodify -x <<EOF
dn:

EOF

It will warn, but allow the modify through.

<Amita>
[root@amsharma reslimit]# ldapmodify -x -h localhost -p 1389 -D "cn=Directory Manager" -w pwd << EOF
dn:

EOF
modifying entry ""
</Amita>

2) You have to be using a server built with mozldap - servers built with
openldap will return an LDAP error when receiving an empty modify request

<Amita>
Sorry, I could not do this as mozldap is deprecated. 
</Amita>

3) Either the modify operation is replicated, or the server has set cn=config
nsslapd-lastmod: off

<Amita>
[root@amsharma reslimit]# ldapsearch -x -h localhost -p 1389 -D "cn=Directory Manager" -w pwd -b "cn=config" | grep nsslapd-lastmod
nsslapd-lastmod: on
[root@amsharma reslimit]# ldapmodify -x -h localhost -p 1389 -D "cn=Directory Manager" -w pwd << EOF
> dn: cn=config
> changetype: modify
> replace: nsslapd-lastmod
> nsslapd-lastmod: off
> EOF
modifying entry "cn=config"

[root@amsharma reslimit]# ldapsearch -x -h localhost -p 1389 -D "cn=Directory Manager" -w pwd -b "cn=config" | grep nsslapd-lastmod
nsslapd-lastmod: off
[root@amsharma reslimit]#
</Amita>

If these conditions are met, the empty modify operation will crash the server.

<Amita>
Server was up and running, no crash found.
I am putting this bug as VERIFIED, please revert in case of any more actions required.
</Amita>

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0533.html