All of lore.kernel.org
 help / color / mirror / Atom feed
* Excluding selected CRYPTO_KEY_USER events
@ 2016-01-09 16:26 Richard Young
  2016-01-09 19:35 ` Steve Grubb
  0 siblings, 1 reply; 2+ messages in thread
From: Richard Young @ 2016-01-09 16:26 UTC (permalink / raw)
  To: linux-audit


[-- Attachment #1.1: Type: text/plain, Size: 388 bytes --]


I know I could exclude all msgtype CRYPTO_KEY_USER audit events, but would
like to exclude just specific ones.
I would like to exclude ones for a specific UID, hostname, or IP.

There are many example of how to exclude specific files, directory events,
or syscall events.

Can somebody suggest a way to suppress specific CRYPTO_KEY_USER events by
UID, hostname, or IP?





[-- Attachment #1.2: Type: text/html, Size: 475 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Excluding selected CRYPTO_KEY_USER events
  2016-01-09 16:26 Excluding selected CRYPTO_KEY_USER events Richard Young
@ 2016-01-09 19:35 ` Steve Grubb
  0 siblings, 0 replies; 2+ messages in thread
From: Steve Grubb @ 2016-01-09 19:35 UTC (permalink / raw)
  To: linux-audit; +Cc: Richard Young

On Saturday, January 09, 2016 10:26:06 AM Richard Young wrote:
> I know I could exclude all msgtype CRYPTO_KEY_USER audit events, but would
> like to exclude just specific ones.
> I would like to exclude ones for a specific UID, hostname, or IP.
> 
> There are many example of how to exclude specific files, directory events,
> or syscall events.
> 
> Can somebody suggest a way to suppress specific CRYPTO_KEY_USER events by
> UID, hostname, or IP?

I opened a bz to ask for this capability a little over a month ago:
https://bugzilla.redhat.com/show_bug.cgi?id=1287745
Unfortunately, I don't think you can do anything until that lands.

This particular event comes from user space. So, the kernel cannot filter on IP 
address. And specifically, the kernel can never really filter on IP address 
because its typically not an argument to any but 2 or 3 syscalls.

There is a chance that you might be able to use the USER filter if the selinux 
type is unique to whatever you wanted to remove.

-a never,user -F subj_type=httpd_t

-Steve

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-01-09 19:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-01-09 16:26 Excluding selected CRYPTO_KEY_USER events Richard Young
2016-01-09 19:35 ` Steve Grubb

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.