From: Eric Paris <eparis@redhat.com>
To: "Miloslav Trmač" <mitr@redhat.com>
Cc: sgrubb@redhat.com, herbert@gondor.hengli.com.au,
linux-audit@redhat.com, linux-crypto@vger.kernel.org
Subject: Re: [PATCH 1/5] Add general crypto auditing infrastructure
Date: Tue, 23 Nov 2010 10:12:31 -0500 [thread overview]
Message-ID: <1290525151.1443.11.camel@localhost.localdomain> (raw)
In-Reply-To: <1290516635-26601-1-git-send-email-mitr@redhat.com>
On Tue, 2010-11-23 at 13:50 +0100, Miloslav Trmač wrote:
> Collect audited crypto operations in a list, because a single _exit()
> can cause several AF_ALG sockets to be closed, and each needs to be
> audited.
>
> Add the AUDIT_CRYPTO_OP field so that crypto operations are not audited
> by default, but auditing can be enabled using a rule (probably
> "-F crypto_op!=0").
Just an implementation question, why a new list instead of finding a way
to reuse struct audit_aux_data?
-Eric
next prev parent reply other threads:[~2010-11-23 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <847856953.215811290516008957.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-11-23 12:47 ` RFC: AF_ALG auditing Miloslav Trmac
2010-11-23 12:50 ` [PATCH 1/5] Add general crypto auditing infrastructure Miloslav Trmač
2010-11-23 15:12 ` Eric Paris [this message]
2010-11-23 18:25 ` Miloslav Trmac
2010-11-23 18:37 ` Eric Paris
2010-11-23 12:50 ` [PATCH 2/5] Add unique IDs to AF_ALG sockets Miloslav Trmač
2010-11-23 12:50 ` [PATCH 3/5] Add "alg_name" operation to af_alg_type Miloslav Trmač
2010-11-23 12:50 ` [PATCH 4/5] Audit type-independent events Miloslav Trmač
2010-11-23 12:50 ` [PATCH 5/5] Audit type-specific crypto operations Miloslav Trmač
2010-11-24 17:05 [PATCH 0/5] RFC v2: AF_ALG auditing Miloslav Trmač
2010-11-24 17:05 ` [PATCH 1/5] Add general crypto auditing infrastructure Miloslav Trmač
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=1290525151.1443.11.camel@localhost.localdomain \
--to=eparis@redhat.com \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-audit@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=mitr@redhat.com \
--cc=sgrubb@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