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
SIGSEV when setting invalid changelog config value #2471
Comments
Comment from tbordaz (@tbordaz) at 2017-10-23 17:43:56 |
Comment from tbordaz (@tbordaz) at 2017-10-23 17:43:58 Metadata Update from @tbordaz:
|
Comment from tbordaz (@tbordaz) at 2017-10-25 11:19:17 |
Comment from tbordaz (@tbordaz) at 2017-10-25 11:19:48 Metadata Update from @tbordaz:
|
Comment from lkrispen (@elkris) at 2017-10-25 12:44:05 I do not fully agree with the patch. It fixes the crash, I assume it is in slapi_is_duration_valid, but haven't seen the stack trace of the crash. But i think:
my proposal would be to either fix slapi_is_duration_valid
|
Comment from tbordaz (@tbordaz) at 2017-10-25 14:44:49 @elkris thank you for looking at it. You are right, I am adding debug info.
The problem is before testing the validity of the value it is in the for loop that assumes it exists values. |
Comment from lkrispen (@elkris) at 2017-10-25 14:56:25 ok. but then I would check before the for J loop and log and return an error |
Comment from tbordaz (@tbordaz) at 2017-10-25 17:48:23 I agree, here a modified patch |
Comment from mreynolds (@mreynolds389) at 2017-10-25 18:00:46 minor requests
|
Comment from lkrispen (@elkris) at 2017-10-25 18:36:24
but this is the returntext explaining "UNWILLING TO PERFORM" to the clients MOD, so it should be clear |
Comment from mreynolds (@mreynolds389) at 2017-10-25 19:58:30
True, I guess I was thinking it was also going to the errors log, but its not. |
Comment from mreynolds (@mreynolds389) at 2017-10-26 17:57:21 Metadata Update from @mreynolds389:
|
Comment from mreynolds (@mreynolds389) at 2017-10-31 14:43:48 Metadata Update from @mreynolds389:
|
Comment from tbordaz (@tbordaz) at 2017-11-07 14:58:44 git push origin master
|
Comment from tbordaz (@tbordaz) at 2017-11-07 15:00:55 Metadata Update from @tbordaz:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49412
Issue Description
The issue is that updating changelog config attribute with a dummy value (leading to empty value) creates a LDAPMod with empty value and crash the server
Package Version and Platform
at least since 1.3.6
Steps to reproduce
Actual results
Crash
Expected results
Should not crash
The text was updated successfully, but these errors were encountered: