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

Slapd SHA256 manager password #21

Open
cimbalo opened this issue Sep 16, 2017 · 2 comments · May be fixed by #26
Open

Slapd SHA256 manager password #21

cimbalo opened this issue Sep 16, 2017 · 2 comments · May be fixed by #26

Comments

@cimbalo
Copy link
Contributor

cimbalo commented Sep 16, 2017

I think slapd use SHA1 for manager password.
Check if we can force it to SHA256.
Related to modification made in commit f0684ce

zolfariot referenced this issue Apr 29, 2020
- Tasks splitted in subfiles.
- Static slapd configuration (slapd.conf) moved *properly* to dynamic
conf (slapd.d).
- TLS Enabled by default, with certificate acquired using
  `ca_manager`.
- New default tree
- New default ACL
- Kerberos schema added
- {SSHA512} hash properly configured.
@zolfariot zolfariot linked a pull request Apr 29, 2020 that will close this issue
@zolfariot
Copy link
Member

Solved by the very BIG PR #26.

Relevant commit:
da88337

In particular,
#r38829224 and #r38829290

@zolfariot
Copy link
Member

Anyway, also salted SHA-2 suite hash functions are not considered good/safe for password storage. Since they are meant for signing/fingerprinting their forward calculation is very fast.

Also, with cryptocurrency using SHA-256 custom hardware with the only purpose of generating very efficiently and quickly SHA-256 hash are commonly available, and it's very easy and fast to generate rainbow tables.

Salted hash seems to mitigate this but it depend on the implementation and the number of rounds used.

It seems that for password hashing algorithms have to be slow. Suggested algorithm are: scrypt, bcrypt, PBKDF2, Argon2.

Argon2 is probably the best and is implemented as a pluggable module in OpenLDAP 2.5.

Probably it can be compiled and backported to stable OpenLDAP 2.4.

Refs:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants