Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1436973 - [DS 10.1.1] PBKDF2_SHA256 password storage scheme
[DS 10.1.1] PBKDF2_SHA256 password storage scheme
Status: CLOSED CURRENTRELEASE
Product: Red Hat Directory Server
Classification: Red Hat
Component: Doc-release-notes (Show other bugs)
10.1
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Marc Muehlfeld
Viktor Ashirov
Marc Muehlfeld
:
Depends On:
Blocks: 1425467
  Show dependency treegraph
 
Reported: 2017-03-29 03:09 EDT by Marc Muehlfeld
Modified: 2017-08-02 02:57 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Directory Server now supports the *PBKDF2_SHA256* password storage scheme To increase security, this update adds the 256-bit password-based key derivation function 2 (PBKDF2_SHA256) to the list of supported password-storage schemes in Directory Server. The scheme uses 30,000 iterations to apply the 256-bit secure hash algorithm (SHA256). Note that the network security service (NSS) database in Red Hat Enterprise Linux prior to version 7.4 does not support PBKDF2. Therefore, you cannot use this password scheme in a replication topology with previous Directory Server versions.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 04:07:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marc Muehlfeld 2017-03-29 03:09:06 EDT
Red Hat Directory Server 10.1.1 adds PBKDF2_SHA256 to the list of supported password storage schemes.

Upstream ticket:
https://pagure.io/389-ds-base/issue/397

This ticket is to document the release note for this feature.
Comment 5 Robert Krátký 2017-04-24 06:10:37 EDT
RN text nitpick fixes.
Comment 7 Marc Muehlfeld 2017-08-01 04:07:26 EDT
The update is now available on the Customer Portal.

Note You need to log in before you can comment on or make changes to this bug.