Fix +1 error in storing krbPrincipalKey LDAP attr. #181
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For principal entries having keys with multiple kvnos (due to use of
-keepold), LDAP backend plugin makes an attempt to store all the keys
having the same kvno into single krbPrincipalKey attribute value.
There is an +1 error in the loop, causing currkvno variable being set
to the just processed value, instead of the next kvno.
As a result, second and all following groups of keys by kvnos are each
stored in two krbPrincipalKey attribute values.
Fixed to use correct kvno value.