The missing-call-to-chdir-with-chroot
test was removed in rpmlint 2.0
83f915a54d
This commit is contained in:
parent
be9fcec798
commit
c4043528c1
@ -40,17 +40,6 @@ addFilter(r'^ruby-libs\.\w+: E: shared-lib-without-dependency-information /usr/l
|
|||||||
# These are Ruby plugins, where Ruby always load glibc prior the library.
|
# These are Ruby plugins, where Ruby always load glibc prior the library.
|
||||||
addFilter(r'^ruby-libs\.\w+: W: library-not-linked-against-libc /usr/lib(64)?/ruby/.*.so$')
|
addFilter(r'^ruby-libs\.\w+: W: library-not-linked-against-libc /usr/lib(64)?/ruby/.*.so$')
|
||||||
|
|
||||||
# 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.N.N.N
|
|
||||||
# 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/.]+$')
|
|
||||||
|
|
||||||
# Rake ships some examples.
|
# Rake ships some examples.
|
||||||
addFilter(r'^rubygem-rake.noarch: W: devel-file-in-non-devel-package /usr/share/gems/gems/rake-[\d\.]+/doc/example/\w+.c$')
|
addFilter(r'^rubygem-rake.noarch: W: devel-file-in-non-devel-package /usr/share/gems/gems/rake-[\d\.]+/doc/example/\w+.c$')
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user