[PATCH 1/5] Add general crypto auditing infrastructure

2010-11-24 Thread Miloslav Trmač
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

Re: [PATCH 1/5] Add general crypto auditing infrastructure

2010-11-23 Thread Eric Paris
On Tue, 2010-11-23 at 13:25 -0500, Miloslav Trmac wrote: > - "Eric Paris" wrote: > > 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 >

Re: [PATCH 1/5] Add general crypto auditing infrastructure

2010-11-23 Thread Miloslav Trmac
- "Eric Paris" wrote: > 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

Re: [PATCH 1/5] Add general crypto auditing infrastructure

2010-11-23 Thread Eric Paris
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

[PATCH 1/5] Add general crypto auditing infrastructure

2010-11-23 Thread Miloslav Trmač
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