[389-announce] Announcing 389 Directory Server version

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


389 Directory Server

The 389 Directory Server team is proud to announce 389-ds-base version for EL6.

EL6-only packages are available, in the Testing repository. It will move to the Stable repositories once it has received some testing from the community. We encourage you to test and provide feedback in order to speed up the push to the Stable repositories.

The new packages and versions are:

  • 389-ds-base-

A source tarball is available for download at http://port389.org/sources/389-ds-base-

Highlights in

In this version, a security bug in ACL, a crash bug in replication, a deadlock issue as well as many important bugs were fixed.  Also, memory management issues reported by valgrind, defects reported by coverity and compiler warnings were fixed.

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 directory server. setup-ds-admin.pl

To upgrade, use yum upgrade yum upgrade After upgrade completes, run setup-ds-admin.pl -u to update your directory server/admin server/console information. setup-ds-admin.pl -u

See Install_Guide for more information about the initial installation, setup, and upgrade

See Source for information about source tarballs and SCM (git) access.


We are very interested in your feedback!

Please provide feedback and comments to the 389-users mailing list: https://admin.fedoraproject.org/mailman/listinfo/389-users

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

Ludwig Krispenz (4):

  • Ticket 47395 47397 v2 correct behaviour of account policy if only stateattr is configured or no alternate attr is configured
  • Ticket 47396 - crash on modrdn of tombstone
  • CVE-2013-2219 ACLs inoperative in some search scenarios - Ticket #47405: defect: access control not working for specific search filter
  • fix compiler warning

Mark Reynolds (19):

  • Ticket 580 - Wrong error code return when using EXTERNAL SASL and no client certificate
  • Coverity Fixes (part 1)
  • Coverity Fixes (Part 2)
  • Coverity Fixes (Part 3)
  • Coverity Fixes (Part 4)
  • Coverity Fixes (Part 5)
  • Coverity Fixes (Part 6)
  • Coverity Fixes (Part 7)
  • Ticket 47385 - DS not shutting down when disk monitoring threshold is reached
  • Ticket 47383 - connections attribute in cn=snmp,cn=monitor is counted twice
  • Ticket 47376 - DESC should not be empty as per RFC 2252 (ldapv3)
  • Ticket 47385 - Disk Monitoring is not triggered as expected.
  • Ticket 47427 - Overflow in nsslapd-disk-monitoring-threshold
  • Ticket 47441 - Disk Monitoring not checking filesystem with logs
  • Ticket 47421 - memory leaks in set_krb5_creds
  • Ticket 47449 - deadlock after adding and deleting entries
  • Ticket 47427 - Overflow in nsslapd-disk-monitoring-threshold

Matthew Via (1):

  • Ticket #47428 - Memory leak in 389-ds-base

Noriko Hosoi (13):

  • Coverity fix 13139 - Dereference after NULL check in slapi_attr_value_normalize_ext()
  • Ticket 623 - cleanAllRUV task fails to cleanup config upon completion
  • Ticket #47347 - Simple paged results should support async search
  • Trac Ticket#531- loading an entry from the database should use str2entry_fast
  • Ticket #47327 - error syncing group if group member user is not synced
  • Ticket #47367 - (phase 1) ldapdelete returns non-leaf entry error while trying to remove a leaf entry
  • Ticket #47391 - deleting and adding userpassword fails to update the password
  • Ticket #47402 - Attribute names are incorrect in search results
  • Ticket #47412 - Modify RUV should be serialized in ldbm_back_modify/add
  • Ticket #47435 - Very large entryusn values after enabling the USN plugin and the lastusn value is negative.
  • Ticket #47378 - fix recent compiler warnings
  • Ticket #543 - Sorting with attributes in ldapsearch gives incorrect result

Rich Megginson (20):

  • Ticket #47362 - ipa upgrade selinuxusermap data not replicating
  • Ticket #47359 - new ldap connections can block ldaps and ldapi connections
  • Ticket #47349 - DS instance crashes under a high load
  • Ticket #47378 - fix recent compiler warnings
  • Ticket #47377 - make listen backlog size configurable
  • Ticket #47375 - flush_ber error sending back start_tls response will deadlock
  • Ticket #47409 - allow setting db deadlock rejection policy
  • Ticket #47410 - changelog db deadlocks with DNA and replication
  • Ticket #47392 - ldbm errors when adding/modifying/deleting entries
  • Ticket #47424 - Replication problem with add-delete requests on single-valued attributes
  • Ticket 47427 - Overflow in nsslapd-disk-monitoring-threshold
  • Fix compiler warnings for Ticket 47395 and 47397
  • fix compiler warning in posix winsync code for posix_group_del_memberuid_callback
  • fix coverity 11895 - null deref - caused by fix to ticket 47392

Thierry bordaz (tbordaz) (2):

  • Ticket 47361 - Empty control list causes LDAP protocol error is thrown
  • Ticket 47393 - Attribute are not encrypted on a consumer after a full initialization
389 announce mailing list

[Index of Archives]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Review]     [Fedora Art]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Art]     [Fedora Docs]

  Powered by Linux