Skip some tests which don't work under permissionless containers

When running as UID 0 but without CAP_DAC_OVERRIDE (for example, in a
docker container running with --uid 0 but --cap-drop=all), these tests
won't work because of hard-coded assumptions about what uid 0 can and
can't do.
This commit is contained in:
KJ Tsanaktsidis 2024-08-08 21:24:13 +10:00
parent 165635049a
commit 8800127d80
Notes: git 2024-08-22 23:34:59 +00:00
2 changed files with 31 additions and 4 deletions

View File

@ -93,12 +93,24 @@ class TestFileUtils < Test::Unit::TestCase
@@no_broken_symlink
end
def has_capsh?
!!system('capsh', '--print', out: File::NULL, err: File::NULL)
end
def has_root_file_capabilities?
!!system(
'capsh', '--has-p=CAP_DAC_OVERRIDE', '--has-p=CAP_CHOWN', '--has-p=CAP_FOWNER',
out: File::NULL, err: File::NULL
)
end
def root_in_posix?
if /cygwin/ =~ RUBY_PLATFORM
# FIXME: privilege if groups include root user?
return Process.groups.include?(0)
end
if Process.respond_to?('uid')
elsif has_capsh?
return has_root_file_capabilities?
elsif Process.respond_to?('uid')
return Process.uid == 0
else
return false

View File

@ -186,6 +186,12 @@ class TestFileExhaustive < Test::Unit::TestCase
@blockdev
end
def root_without_capabilities?
return false unless Process.uid == 0
return false unless system('command', '-v', 'capsh', out: File::NULL)
!system('capsh', '--has-p=CAP_DAC_OVERRIDE', out: File::NULL, err: File::NULL)
end
def test_path
[regular_file, utf8_file].each do |file|
assert_equal(file, File.open(file) {|f| f.path})
@ -1538,8 +1544,17 @@ class TestFileExhaustive < Test::Unit::TestCase
assert_equal(stat.size?, File.size?(f), f)
assert_bool_equal(stat.socket?, File.socket?(f), f)
assert_bool_equal(stat.setuid?, File.setuid?(f), f)
assert_bool_equal(stat.writable?, File.writable?(f), f)
assert_bool_equal(stat.writable_real?, File.writable_real?(f), f)
# It's possible in Linux to be uid 0, but not to have the CAP_DAC_OVERRIDE
# capability that allows skipping file permissions checks (e.g. some kinds
# of "rootless" container setups). In these cases, stat.writable? will be
# true (because it always returns true if Process.uid == 0), but
# File.writeable? will be false (because it actually asks the kernel to do
# an access check).
# Skip these two assertions in that case.
unless root_without_capabilities?
assert_bool_equal(stat.writable?, File.writable?(f), f)
assert_bool_equal(stat.writable_real?, File.writable_real?(f), f)
end
assert_bool_equal(stat.executable?, File.executable?(f), f)
assert_bool_equal(stat.executable_real?, File.executable_real?(f), f)
assert_bool_equal(stat.zero?, File.zero?(f), f)