Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] Support enhanced crypt(3) password hashes #312

Closed
389-ds-bot opened this issue Sep 12, 2020 · 4 comments
Closed

[RFE] Support enhanced crypt(3) password hashes #312

389-ds-bot opened this issue Sep 12, 2020 · 4 comments
Labels
closed: duplicate Migration flag - Issue

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/312


It would be useful if the CRYPT password storage scheme included support
for the MD5 or SHA256 password hashes on platforms whose underlying
crypt(3) implementation supports them.

This would allow for longer, stronger while retaining compatibility with
most modern Unix-like operating systems, such as Linux, *BSD, and
Solaris.

For example, Sun DSEE 6 uses nsslapd-pluginarg0 to specify a format
string used to generate the password's salt:

nsslapd-pluginarg0: $1$%.8s$

However, it might be preferable for the parameter to take a value such
as MD5 or SHA256.

In our environment, this is needed to support systems which do not
directly use LDAP, but have the password hashes from the LDAP servers
propagated to them on an as-needed basis.

@389-ds-bot 389-ds-bot added the closed: duplicate Migration flag - Issue label Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-03-02 04:43:08

Is this a duplicate of https://fedorahosted.org/389/ticket/131 ?

@389-ds-bot
Copy link
Author

Comment from imorgan at 2012-03-02 05:52:30

Replying to [comment:1 richm]:

Is this a duplicate of https://fedorahosted.org/389/ticket/131 ?

Yes, sorry about that.

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2012-08-28 04:14:41

Added initial screened field value.

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2017-02-11 22:51:49

Metadata Update from @nkinder:

  • Issue assigned to richm
  • Issue set to the milestone: N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: duplicate Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant