The 389 Directory Server team is proud to announce 389-ds-base version
Fedora packages are available from the Fedora 18 Testing repositories.
It will move to the Fedora 18 Stable repositories once it has received
enough karma in Bodhi. We encourage you to test and provide feedback
here in order to speed up the push to the Stable repositories.
The new packages and versions are:
A source tarball is available for download at
Highlights in 22.214.171.124
Fixed security issue with invalid controls.
Fixed crash casued by trying to delete a tombstone entry.
Fixed issue where the dse.ldif can get corrupted.
Fixed erroneous error message from WinSync.
Improved DNA plugin startup process.
Fixed issue where an invalid chaining plugin configuration would
accidentally casue the server to shutdown.
Fixed issue with replication interfering with certain modify
Fixed some ememory leaks.
Fixed issue with the PAM plugin schema not being upgraded correctly.
Installation and Upgrade
See Download for information about setting up your yum repositories.
To install, use yum install 389-ds
yum install 389-ds
After install completes, run setup-ds-admin.pl to set up your
To upgrade, use yum upgrade
After upgrade completes, run setup-ds-admin.pl -u to update your
directory server/admin server/console information.
We are very interested in your feedback!
Please provide feedback and comments to the 389-users mailing list:
If you find a bug, or would like to see a new feature, file it in
our Trac instance: https://fedorahosted.org/389
Detailed Changelog since 126.96.36.199
Noriko Hosoi (5):
Bug 912964 - CVE-2013-0312 389-ds: unauthenticated denial of
service vulnerability in handling of LDAPv3 control data
Ticket 579 - Error messages encountered when using POSIX winsync
Ticket 576 - DNA: use event queue for config update only at the
Ticket 572 - PamConfig schema not updated during upgrade
Bug 906005 - Valgrind reports memleak in
Mark Reynolds (4):
bump version to 188.8.131.52
Ticket 570 - DS returns error 20 when replacing values of a
multi-valued attribute (only when replication is enabled)
Ticket 590 - ns-slapd segfaults while trying to delete a tombstone
Ticket 367 - Invalid chaining config triggers a disk full error and
Ludwig Krispenz (1):
Ticket #518 - dse.ldif is 0 length after server kill or machine kill
Red Hat, Inc