selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dominick Grift <dac.override@gmail.com>
To: Ian Pilcher <arequipeno@gmail.com>
Cc: selinux@vger.kernel.org
Subject: Re: execve silently blocked
Date: Wed, 2 Oct 2019 21:41:00 +0200	[thread overview]
Message-ID: <20191002194100.GB1167620@brutus.lan> (raw)
In-Reply-To: <43c6d9cc-bf9f-b729-2a0c-54a73fa79fdc@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

On Wed, Oct 02, 2019 at 02:25:22PM -0500, Ian Pilcher wrote:
> I am writing an SELinux policy for a daemon that needs to exec an
> external program.  The execve call is being denied (permission denied),
> but no denial is being logged, even after disabling dontaudit rules
> (semodule -DB).

Are you also looking for "selinux_err" records?

`ausearch -m avc,user_avc,selinux_err -i`

will return avc, user_avc and selinux_err records if auditd is running.

> 
> (The execve call does succeed in permissive mode.)
> 
> How can I troubleshoot this?
> 
> Thanks!
> 
> -- 
> ========================================================================
> Ian Pilcher                                         arequipeno@gmail.com
> -------- "I grew up before Mark Zuckerberg invented friendship" --------
> ========================================================================

-- 
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2019-10-02 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-02 19:25 execve silently blocked Ian Pilcher
2019-10-02 19:41 ` Dominick Grift [this message]
2019-10-02 20:08   ` Ian Pilcher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191002194100.GB1167620@brutus.lan \
    --to=dac.override@gmail.com \
    --cc=arequipeno@gmail.com \
    --cc=selinux@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).