public inbox for linux-audit@redhat.com
 help / color / mirror / Atom feed
From: Steve Grubb <sgrubb@redhat.com>
To: "Todd, Charles" <CTODD@ball.com>
Cc: Linux Audit <linux-audit@redhat.com>
Subject: Re: stime(2) auditing on x86_64
Date: Mon, 29 Oct 2007 09:11:52 -0400	[thread overview]
Message-ID: <200710290911.52675.sgrubb@redhat.com> (raw)
In-Reply-To: <C482FF98AE985A47B8C982FD429C9E3401370F5D@daytonmsg2k3.AERO.BALL.COM>

On Sunday 28 October 2007 05:51:03 pm Todd, Charles wrote:
> > That is because x86_64 does not have that syscall. It uses
> > settimeofday for the same functionality. But, it does exist
> > in the 32 bit compatibility layer.
>
> Okay, I understand the bi-arch thing except one thing: does that mean
> the 32-bit compatability layer is ultimately calling the 64-bit version?

Somewhere deeper inside, they probably share some code. But the audit hooks 
are at the entry/exit to the syscall. So, covering one does not cover the 
other. As Matt mentioned, you need 2 syscall rules explicitly stating bit 
size.


> > Not really, I think DISA is telling you the intent and that
> > needs to be interpretted/extended to cover bi-arch systems. 
>
> DISA's intent and their SRRs have always been two completely separate
> entities.  Testers only see that I don't have that flag, and less
> resourceful security folks won't know how to argue back.  Ultimately, we
> need to teach DISA to write better tests.

I'll be updating the sample audit rule sets in the next release to reflect 
both the subtree audit capability (since that's now merged in 2.6.24) and the 
bit sizing. Hopefully this updated rule set will trickle down to the right 
places.

-Steve

      parent reply	other threads:[~2007-10-29 13:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-27  4:29 stime(2) auditing on x86_64 Todd, Charles
2007-10-27 14:55 ` Steve Grubb
2007-10-28 21:51   ` Todd, Charles
2007-10-28 22:46     ` Matthew Booth
2007-10-29 13:11     ` Steve Grubb [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=200710290911.52675.sgrubb@redhat.com \
    --to=sgrubb@redhat.com \
    --cc=CTODD@ball.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