Thanks for clarifying. I was just checking Your recent commits to json-c and found #393 that seemed to be related. To be clear: I am not aware of anything that should be fixed but isn't.
Well, this update will not be submitted for stable, before sway and libu2f-server are submitted for stable; those needed some critical fix for not being broken by this as well.
For this reason auto-push is disabled here.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
This update has been submitted for testing by besser82.
This update has been pushed to testing.
No regressions noticed.
Works
besser82 edited this update.
Hallo,
from Your dscription I deduce that You're talking about this issue:
https://github.com/json-c/json-c/pull/389
Is this the correct one and is anything else fixed?
Cheers
Yes, that is the addressed issue here. What do you mean by
anything else fixed?works for me
Thanks for clarifying. I was just checking Your recent commits to json-c and found #393 that seemed to be related. To be clear: I am not aware of anything that should be fixed but isn't.
Well, this update will not be submitted for stable, before sway and libu2f-server are submitted for stable; those needed some critical fix for not being broken by this as well.
For this reason auto-push is disabled here.
This update has reached the stable karma threshold and can be pushed to stable now if the maintainer wishes.
Is a CVE related to this bug? And if not, why is this update tagged as security?
Works fine for me.
This update has been submitted for stable by besser82.
This update has been pushed to stable.