Kentaro Hayashi
Kentaro Hayashi
@ReillyBrogan PR is welcome!
Thanks, @Simon-Janos Do you know whether this issue is assigned to CVE-*?
To be clear, if `dir_permission` was specified (like the above example), is it not vulnerable?
FYI: since v1.2.0, https://github.com/fluent/fluentd/blob/master/CHANGELOG.md#release-v120---20180430 [output: Backup for broken chunks](https://github.com/fluent/fluentd/pull/1952) is supported. It may help you.
I'll simplify test case.
TODO: check plugin gemdir.
What is the good way to detect dummy plugin? Just idea: launch fluentd with `--gem-path ` and put dummy plugin for it. But Gem::Specification.find_all can't detect it. :thinking:
Even though launched via `assert_fluentd_fails_to_start` with --gemfile, it cause an error with " error: You seem to use `bundle exec` already." It seems that BUNDLE_BIN_PATH checked and exit there.
According to https://github.com/ruby/openssl/issues/603 and https://github.com/ruby/openssl/releases/tag/v3.2.0, all of FIPS support effort is not fully merged in v3.2.0, so need to wait newer ruby/openssl release. (e.g. https://github.com/ruby/openssl/pull/694 was fixed after v3.2.0) As...
Hmm, GitHub "update branch" feature is not what I want. rebased manually.