-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
About Onigmo #6000
Comments
Yes, can you make PRs? The more general solution may be to switch to Oniguruma https://github.com/kkos/oniguruma |
thanks everybody for addressing this. Before submitting the PR directly to the bundled library, I think it's important to understand the Onigmo situation:
|
Ruby still uses onigmo. They are bundled onigmo as normal sources like as other Ruby's sources:
The main downside is: there is a possibility to change supported regular expression format. I'm not sure what is added feature in Onigmo instead of Oniguruma. |
got it, we cannot break regexes, I recall there was some special regex features for Ruby that also Fluentd relies on. So I think it would be better to keep our own updated version. @cosmo0920 do you know if the original developer can be contacted locally there in JP ? |
Thanks @sashashura -- @edsiper will carry this forward in terms of to patch or not. One thing we should consider is whether patching is sustainable, as the fuzzers may continue to keep finding issues in the library. |
I've cloned the original Onigmo in our own fluent/ organization, just with the purpose to have all these patches-in. would you please submit the PRs to the new repo instead? |
I'm not sure where is he living and working in. But, his twitter (in Japanese) https://twitter.com/k_takata is still active. |
I'd sent message to him on Twitter. (In Japanese): https://twitter.com/cosmo__/status/1566973012733493249 |
|
thanks everyone! everything has been merged on https://github.com/fluent/onigmo we also added CMake support into onigmo, merged into Fluent Bit: |
I wonder what is your opinion about fixing fluent-bit memory access bugs when the root cause is Onigmo.
At this moment I have identified two such cases and submitted the patches: k-takata/Onigmo#164 and k-takata/Onigmo#165. However after almost two months there is no response and the last time somebody has pushed anything to the project is Feb 4, 2021.
From security point of view attackers don't really care in which library invalid memory access happens, as long as is in the program they exploit. Do you think it is a good idea to patch Onigmo locally in https://github.com/fluent/fluent-bit/tree/master/lib/onigmo until the official library provides the fix?
cc: @DavidKorczynski
The text was updated successfully, but these errors were encountered: