From: Steve Grubb <sgrubb@redhat.com>
To: "warron.french" <warron.french@gmail.com>
Cc: Linux-Audit Mailing List <linux-audit@redhat.com>
Subject: Re: Auditing printing
Date: Tue, 01 May 2018 17:53:52 -0400 [thread overview]
Message-ID: <17945387.OdX4JIY6fL@x2> (raw)
In-Reply-To: <CAJdJdQnUCmGgMOKp-JrXUSau283YrK8-i1hnV7yXZxPkGDYrbQ@mail.gmail.com>
On Tuesday, May 1, 2018 2:29:56 PM EDT warron.french wrote:
> OK, so that will cover from CLI as well as something in the gui like
> Firefox?
>
> For both printing to a print device as well as to a file?
I haven't looked at this code in a very long time. So, I don't remember how
to enable it to test it. But it should have full coverage to meet export
requirements for LSPP way back on RHEL 5. The code has been ported all these
years and is supposed to still work.
-Steve
> On Tue, May 1, 2018 at 2:20 PM, Steve Grubb <sgrubb@redhat.com> wrote:
> > On Tuesday, May 1, 2018 2:05:36 PM EDT warron.french wrote:
> > > I have a requirement to monitor two (2) things:
> > >
> > > 1. Print to file
> > >
> > > 2. Print to (printer) device
> > >
> > >
> > > What is the best approach for this?
> >
> > Cups should be hardwired to audit.
> >
> > # ldd /usr/sbin/cupsd | grep audit
> >
> > libaudit.so.1 => /lib64/libaudit.so.1 (0x00007f04f1cfa000)
> >
> > It's been a long time since I looked at this.
> >
> > -Steve
> >
> > > I don't see a syscall that looks
> > > appropriate - but that doesn't mean there is not one.
> > >
> > > Would I simply do an audit on the *lpr* command? Or is it another
> >
> > command?
> >
> > > I need the ability to monitor printing to both file and device, *FROM*,
> > > linux shell as well as console or GUI.
> > >
> > > Can someone advise me on how to accomplish this please?
> > >
> > >
> > > Thanks in advance,
> > > --------------------------
> > > Warron French
next prev parent reply other threads:[~2018-05-01 21:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 18:05 Auditing printing warron.french
2018-05-01 18:20 ` Steve Grubb
2018-05-01 18:29 ` warron.french
2018-05-01 21:53 ` Steve Grubb [this message]
2018-05-01 23:57 ` warron.french
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=17945387.OdX4JIY6fL@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.com \
--cc=warron.french@gmail.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