Table 2. List of Bugs Fixed in 9.0
Bug Number Descript ion
151705 The Admin Server Console is hard-coded to set
all T LS ciphers to enabled. Disabling the T LS
ciphers through the Console is not saved, and
the ciphers are re-enabled when the Admin
Server is restarted.
472131
564448
Directory Server stores entry IDs in an ID list in a
duplicate btree. If the ID list is very long, the
internal database uses internal pages to sort the
entries. When verifying database data, Berkeley
DB's verify function returns out-of-order key
errors because the database verification does
not differentiate between the duplicate btree ID
list and the main tree entry pages. T he database,
then, incorrectly tries to compare the main
database page to itself rather than the duplicate
ID btree. T his affects Directory Server client tools
such as verify-db.pl and dbverify.
This issue has been fixed in BerkeleyDB 4.8.26.
However, the fix will not be available for Red Hat
Enterprise Linux 4 and is not yet available for Red
Hat Enterprise Linux 5. It will be addressed for
Red Hat Enterprise Linux 5 systems in later
errata.
494944 If a gidNumber attribute was deleted from a
replicated entry and more than one supplier was
configured with the DNA Plug-in, then both
masters would assign a new gidNumber value.
505722 An Active Directory group with a mail attribute
could not be synced over to Directory Server.
522055 If an entry was moved outside the scope of the
Linked Attributes Plug-in, the linked attributes
were still updated.
596521 Import operations encounter fatal failures on
some environments when trying to create an
index for more than 200 attributes.
616850 An ldapm odify command failed to reject a
replace operation for an unknown attribute.
618897 The Directory Server Console could not manage
certificates if there were several instances
configured on a machine with different system
user IDs, even if they used the same group
account.
623118 A simple paged search went into an infinite loop if
the search base had a subsuffix.
668619 A high volume of T CP traffic could cause the
slapd process to quit responding to clients.
Comentarios a estos manuales