public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Tony Jones <tonyj@suse.de>
To: Eric Paris <eparis@redhat.com>
Cc: linux-audit@redhat.com
Subject: Re: Rational behind RefuseManualStop=yes in auditd.service
Date: Wed, 18 Dec 2013 13:16:11 -0800	[thread overview]
Message-ID: <52B2109B.9070802@suse.de> (raw)
In-Reply-To: <52B20E89.1050706@suse.de>

On 12/18/2013 01:07 PM, Tony Jones wrote:
> On 12/18/2013 12:38 PM, Eric Paris wrote:
> 
>> He made the change in the upstream repo, because that's what you need
>> for certification purposes.  Personally, I hate it, cause i don't give a
>> hoot about that and would rather things to be consistent, but that's the
>> rational.  A certifiable audit needs what he has in the repo.  If we
>> ever get all of the credential data available to systemd it can be
>> reverted...
> 
> This doesn't really make a lot of sense as a certifiable audit presumably also needs the local Fedora specific changes to systemd, which are not in the upstream systemd repo.   So I'd have thought the Fedora specific audit package was a perfectly suitable location for the audit changes rather than the main audit svn repo.

OIC, you were talking purely of the addition of the RefuseManualStop=yes,   Sorry,   I was talking more about the presence of utility scripts in the svn repo that are Fedora specific since they rely on Fedora systemd extensions.

Anyhow, as I said, not a big deal.  Thanks for reply.

      reply	other threads:[~2013-12-18 21:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 20:04 Rational behind RefuseManualStop=yes in auditd.service Laurent Bigonville
2013-07-30 20:25 ` Steve Grubb
2013-12-03 20:16   ` Tony Jones
2013-12-18 20:38     ` Eric Paris
2013-12-18 21:07       ` Tony Jones
2013-12-18 21:16         ` Tony Jones [this message]

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=52B2109B.9070802@suse.de \
    --to=tonyj@suse.de \
    --cc=eparis@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