From 2c0683f1178e85bb0315197d8cc9d2335ccb79a2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?V=C3=ADt=20Ondruch?= Date: Tue, 4 Jan 2022 18:54:59 +0100 Subject: [PATCH] Remove `missing-call-to-chdir-with-chroot` from rpmlint filter. This test was removed in rpmlint 2.0.0: https://github.com/rpm-software-management/rpmlint/pull/219 --- ruby.rpmlintrc | 11 ----------- 1 file changed, 11 deletions(-) diff --git a/ruby.rpmlintrc b/ruby.rpmlintrc index bc72c06..4d4e67a 100644 --- a/ruby.rpmlintrc +++ b/ruby.rpmlintrc @@ -40,17 +40,6 @@ addFilter(r'^rubygem-rbs\.noarch: E: non-executable-script /usr/share/gems/gems/ # test-unit addFilter(r'^rubygem-test-unit\.noarch: E: non-executable-script /usr/share/gems/gems/test-unit-[\d\.]+/test/run-test.rb 644 ') -# The function `chroot` without using `chdir` is detected by rpmlint with the -# following message. However it looks a false positive as the `chroot` in the -# `dir.c` is just used as a Ruby binding `Dir.chroot` for the function. -# -# ruby-libs.x86_64: E: missing-call-to-chdir-with-chroot /usr/lib64/libruby.so.3.0.1 -# This executable appears to call chroot without using chdir to change the -# current directory. This is likely an error and permits an attacker to break -# out of the chroot by using fchdir. While that's not always a security issue, -# this has to be checked. -addFilter(r'^ruby-libs\.\w+: E: missing-call-to-chdir-with-chroot /usr/lib(64)?/libruby.so.[\d/.]+$') - # Nothing referred and no dependency information should be no problem. # https://bugs.ruby-lang.org/issues/16558#note-2 addFilter(r'^ruby-libs\.\w+: E: shared-lib-without-dependency-information /usr/lib(64)?/ruby/enc/gb2312.so$')