On Wed, 16 May 2018 13:25:55 -0400 m.roth@xxxxxxxxx wrote: > And why, for that matter, does running sealert give me the full path > to the executable, like openjdk... but *not* the full path to the > file it's trying to operate on, and I'm left going "ok, where was the > file it deleted? Ok, there is a current working directory and a relative path, but I believe that in such cases, the SELinux denial or error is thrown before the full path to the file is even spelled out or made available for the application. -- https://www.colmena.biz/~justina/contacto.php
Attachment:
pgpE1rx1ZYTSL.pgp
Description: OpenPGP digital signature
_______________________________________________ selinux mailing list -- selinux@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to selinux-leave@xxxxxxxxxxxxxxxxxxxxxxx
