From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: [PATCH 1/1] audit: log binding and unbinding to netlink multicast
Date: Mon, 16 Oct 2017 18:28:50 -0400 [thread overview]
Message-ID: <2996118.lXGmUDsRlS@x2> (raw)
In-Reply-To: <18408080.ZMkQbuXcMZ@x2>
On Monday, October 16, 2017 6:06:47 PM EDT Steve Grubb wrote:
> > > +/* Log information about who is connecting to the audit multicast
> > > socket
> > > */ +static void audit_log_multicast_bind(int group, const char *op, int
> > > err) +{
> > > + const struct cred *cred;
> > > + struct tty_struct *tty;
> > > + char comm[sizeof(current->comm)];
> > > + struct audit_buffer *ab;
> > > +
> > > + ab = audit_log_start(NULL, GFP_KERNEL, AUDIT_EVENT_LISTENER);
> >
> > It really seems like this should be associated with the current task,
> > e.g. "audit_log_start(current->audit_context, ...)". After all, the
> > whole point of this record is to capture information about the subject
> > who is binding to the multicast socket.
>
> OK, easy enough.
But wouldn't that make it an auxiliary record (if there happens to be a
syscall record) instead of a standalone event? The intention is that this
event is standalone just like AUDIT_SECCOMP or AUDIT_LOGIN. Associating with
the current task is done by using current in formatting the message as seen
below. (e.g. task_pid_nr(current), audit_get_sessionid(current))
I think it's correct as is.
-Steve
> > + if (!ab)
> > + return;
> > +
> > + cred = current_cred();
> > + tty = audit_get_tty(current);
> > +
> > + audit_log_format(ab, "pid=%u uid=%u auid=%u tty=%s ses=%u",
> > + task_pid_nr(current),
> > + from_kuid(&init_user_ns, cred->uid),
> > + from_kuid(&init_user_ns,
> > audit_get_loginuid(current)), + tty ? tty_name(tty)
> > : "(none)",
> > + audit_get_sessionid(current));
> > + audit_put_tty(tty);
> > + audit_log_task_context(ab); /* subj= */
> > + audit_log_format(ab, " comm=");
> > + audit_log_untrustedstring(ab, get_task_comm(comm, current));
> > + audit_log_d_path_exe(ab, current->mm); /* exe= */
next prev parent reply other threads:[~2017-10-16 22:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 19:58 [PATCH 1/1] audit: log binding and unbinding to netlink multicast Steve Grubb
2017-10-16 18:56 ` Richard Guy Briggs
2017-10-16 19:09 ` Richard Guy Briggs
2017-10-16 21:35 ` Paul Moore
2017-10-16 22:06 ` Steve Grubb
2017-10-16 22:28 ` Steve Grubb [this message]
2017-10-16 23:04 ` Richard Guy Briggs
2017-10-17 3:37 ` Steve Grubb
2017-10-17 14:56 ` Paul Moore
2017-10-17 15:11 ` Paul Moore
2017-10-17 16:01 ` Steve Grubb
2017-10-17 16:39 ` Paul Moore
2017-10-17 14:51 ` Paul Moore
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=2996118.lXGmUDsRlS@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.