Conversation
|
@ghen2 Could you please review this ? |
|
This is now running in our lab, as a drop-in upgrade (no slapcat/slapadd performed), I will test further. A few remarks:
|
@ghen2 Thank you for your review. |
|
Not on CentOS/RHEL 7: |
yes correct, need to check why zimbra-perl-net-ldapapi is not linked to zimbra openldap on CentOS/RHEL 7 |
|
@quanah can you please review this ? |
ghen2
left a comment
There was a problem hiding this comment.
Best do the chown root:zimbra and chmod 750 here as well (first), or it will revert the setcap later (see comments in zmfixperms).
@ghen2 have you tested this by enabling olcIndexHash64 ( 64 bit hash for indexing ) ? |
No, we use default 32 bit index hashes (I did not know this option). |
It's a fairly new option but will become the default in the future. Setting it requires a full DB reload. I'd strongly advise that a full review of the features and changes in OpenLDAP 2.5 is done prior to 2.5 being integrated, as there likely should be a one-time database export/import as a part of the upgrade process. Some upgrade items would likely require a zmlocalconfig key, but I wouldn't suggest one for the 64 bit index hashes, there's no reason to go backwards to 32-bit ones. |
Hi Quanah Previously you said an export/import is not required: #118 (comment), and we are indeed running this 2.5.13 Zimbra build as a drop-in replacement for 2.4 in our non-prod environments. Or are you only suggesting this as part of a broader upgrade that also changes database configuration, like index_hash64 (and possibly others) ? But such changes could be done separately from the 2.5 upgrade itself? Geert |
Hi Geert! I'm saying that it may be worthwhile where this is done for the Zimbra product as a whole, to take advantage of the new tuning options and do the necessary one time database reload. I'd also ensure the new feature to slapo-unique to serialize mod ops is implemented. The DB reload is certainly not required now, but will be at some point in the future when the 64-bit index hashes are turned on by default. It would help with very large customer bases in particular. |
|
The ARGON2 change would only affect new password changes though, so nothing would break for existing users as long as they haven't changed their passwords. Since LDAP nodes are the first things that must be upgraded in a deployment, I think the risk there is relatively low (i.e., should only be a spate of minutes where it's even possible that someone who just changed their password would run the risk of not being able to authenticate). |
|
Only if all LDAP's are upgraded in the same maintenance window - which I wasn't assuming, but could indeed be considered a requirement. |
|
I don't know how Zimbra's changed vs the past, but IIRC it was always a documented requirement that all LDAP nodes be updated during the same window. |
) * Update libsodium to 1.0.18 for argon2 support. * Update OpenLDAP to 2.4.50 (for new pw-argon2 password module). * Build OpenLDAP pw-argon2 module to support the Argon2 key derivation function. See https://en.wikipedia.org/wiki/Argon2 for more information, and contrib/slapd-modules/passwd/argon2/README for OpenLDAP specific notes. Requires OpenLDAP >= 2.4.50 and libsodium >= 1.0.9. olcPasswordHash can be set to {ARGON2} (from current {SSHA512}) to use argon2 password hashes by default. * Update for OpenLDAP 2.4.56 * This bit was already there. * 2.4.56 * Fix compilation error 2.4.56 * Fix compilation * Upgrade openldap-2.4.56. * Openldap upgraded to 2.4.59 * Require libsodium >= 1.0.18 * The argon2 module is now part of OpenLDAP 2.5, no longer a contrib module. * The argon2 module is now part of OpenLDAP 2.5, no longer a contrib module. debian version not tested. Co-authored-by: Quanah Gibson-Mount <quanah@symas.com> Co-authored-by: Prashantsurana <prashant.surana@synacor.com> Co-authored-by: Prashant Surana <p.k.surana@gmail.com> Co-authored-by: Umashankar Avagadda <umagmrit@gmail.com>
|
If possible squash and reduce number of commits before merging this PR |
|
Hi Any idea when this will be merged? (it has been running in our lab for months without issues, as a drop-in replacement for 2.4) |
|
Can you please rebase this on OpenSSL 3.0.9 ? |
|
I created a separate PR #192 for the libsodium upgrade, so we can more easily add Argon2 support to either OpenLDAP 2.4 or 2.5, independent of this PR (as we're already using this). |
|
@silentsakky @umagmrit Can you please consider the separate libsodium upgrade already? Makes our local argon2 build easier to maintain. |
No description provided.