-
Notifications
You must be signed in to change notification settings - Fork 377
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
Error loading libddwaf when using generic ruby platform #4077
Comments
Hey @luc-financeit 👋🏼 Thanks for reporting, this is indeed an unintentional mistake which will be fixed ASAP |
@luc-financeit If you can, I would like to ask you to share a single top block of your
And also output of the I think it might be another issue with installation. It would be good to be able to reproduce it. |
@luc-financeit Good news, we have released v2.6.0 with a fix. But I would still appreciate some details about your bundler. |
Can confirm 2.6.0 fixes the issue, thanks! Here's the additional bundler info:
|
Happy to hear that! We will take a look into installation process to see possible issues there. I'm going to close this issue with a follow up issue in DataDog/libddwaf-rb#60 |
Current behaviour
After upgrading from 2.4.0 to 2.5.0, I'm seeing an error at boot time loading
libddwaf
:Error & Backtrace
Expected behaviour
No crash.
Steps to reproduce
For reasons unknown, I had
BUNDLE_FORCE_RUBY_PLATFORM=true
in my shell profile, so I ended up installing a version of thelibddwaf
gem with no pre-built binaries. From a quick skim of thedatadog
source code, it looks like this might have worked in 2.4 becauselibddwaf
was not loaded unless AppSec was enabled and/or load errors were rescued, whereas in 2.5libddwaf
is being loaded unconditionally? I've put together a minimal Rails app that reproduces the issue; see instructions in the README.In all honesty, I don't know why I had
BUNDLE_FORCE_RUBY_PLATFORM=true
in my profile, and I've resolved the issue for myself by just removing that env var. Just thought it was maybe worth a mention anyways; if nothing else, it seems odd forAppSec::Processor
to use such precaution loadinglibddwaf
whenappsec/processor/context.rb
has already loaded it 🤷♂Environment
The text was updated successfully, but these errors were encountered: