From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: krb5 issues
Date: Thu, 26 May 2016 16:04:49 -0400 [thread overview]
Message-ID: <5883713.JF5uphcy4a@x2> (raw)
In-Reply-To: <57471335.3010406@kenbass.com>
On Thursday, May 26, 2016 11:16:05 AM Ken Bass wrote:
> On 05/24/2016 10:07 AM, Ken Bass wrote:
> > On a related note, using krb5 causes a problem with selinux. Unless I
> > disable it (or figure out a rule) auditd fails to start because it is
> > denied permission to create /var/tmp/auditd_0 kerberos replay cache file.
> > Is there a rule or procedure to properly fix that?
>
> Is there somewhere to file a bug report for this at?
You could use Bugzilla and file against selinux-policy.
> Obviously the selinux is not being setup for auditd to manage the
> /var/tmp/auditd_0 file when krb5 is enabled. Using Centos 7.2.
I think its used so rarely that no one has noticed.
-Steve
next prev parent reply other threads:[~2016-05-26 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 15:21 krb5 issues Ken Bass
2016-05-24 14:07 ` Ken Bass
2016-05-26 15:16 ` Ken Bass
2016-05-26 20:04 ` Steve Grubb [this message]
2016-05-26 20:12 ` Steve Grubb
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=5883713.JF5uphcy4a@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
/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).