Göran Uddeborg wrote:
Göran Uddeborg writes:
> I retriggered it, and attach the mail setroubleshoot sent me.
It looked wierd in my mail client when I got it back. I'm not sure
why, and if its buggy when reading or when writing. Just in case, I
reran sealert and include the output below.
Summary:
SELinux is preventing ln (user_t) "link" to
./30392D30342D3132202D20535654312056C3A473746E797474202D204D65726C696E202D20427269747469736B742066616E746173796472616D615F2044656C2031332061762031335F2056C3A46E736B61705F206C6F6A616C69746574206F6368206B2E7473
(var_lib_t).
Sometimes the kernel audit system encodes strings as hex if there are
any unusual characters in the string (including a space). setroubleshoot
is supposed to automatically turn hex encoded strings back into a
string, but it looks like in this instance it didn't. The string is
actually:
09-04-12 - SVT1 V\xc3\xa4stnytt - Merlin - Brittiskt fantasydrama_ Del
13 av 13_ V\xc3\xa4nskap_ lojalitet och k.ts
--
John Dennis <jdennis(a)redhat.com>
Looking to carve out IT costs?
www.redhat.com/carveoutcosts/