f5c43be61e
Restore the restorecond service to its original state. The restorecond service should not stay running if it was not running before execution of the test.
24 lines
847 B
Text
24 lines
847 B
Text
path: /policycoreutils/restorecond_pointer_abuse
|
|
summary: Does restorecond flood journal with "blob data" messages?
|
|
description: |
|
|
This test creates mislabeled files and runs restorecond repeatedly to test
|
|
for an issue caused by overwriting program variable with memory address.
|
|
The issue caused restorecond to write status messages (that appeared
|
|
as "blob data" because of \r character) to journal.
|
|
|
|
Since the memory address mentioned above is effectively random data,
|
|
this test may result in SUCESS even if the issue being tested is present!
|
|
|
|
Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=1626468
|
|
component:
|
|
- policycoreutils
|
|
recommend:
|
|
- git-core
|
|
- policycoreutils-restorecond
|
|
- coreutils
|
|
- systemd
|
|
- policycoreutils
|
|
- libselinux-utils
|
|
adjust:
|
|
- enabled: false
|
|
when: distro < rhel-7
|