From: Steve Grubb <sgrubb@redhat.com>
To: Linux Audit <linux-audit@redhat.com>
Subject: Audit Blog
Date: Tue, 14 Feb 2017 22:38:50 -0500 [thread overview]
Message-ID: <14726585.OljHlpHYv1@x2> (raw)
Hello,
I have started the blog to discuss audit issues at this location:
http://security-plus-data-science.blogspot.com/
I only have a basic sketch of the direction this will go for now. But I will
start posting there regularly - especially for the next couple of weeks while
I'm unloading all the information about the new audit capabilties. Feel free
to ask questions here to be expanded on there.
-Steve
reply other threads:[~2017-02-15 3:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14726585.OljHlpHYv1@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.