On Tue, 2008-03-04 at 23:02 -0500, [EMAIL PROTECTED] wrote:
On Tue, 04 Mar 2008 14:05:36 EST, Eric Paris said:
Like it or not I will not accept any kernel patch which causes a new
kernel to break SELinux usability with FC2 userspace. read that again.
OK, I'll bite - at what point has
Tomas Mraz napsal(a):
This proposal is just for starting the discussion.
1. Messages contain name=value pairs separated by spaces.
2. All names are just alphanumeric sequences.
3. Values can be either:
a) byte sequences with the following special characters encoded as %XX
where XX is
On Wed, 2008-03-05 at 14:55 +0100, Miloslav Trmac wrote:
Tomas Mraz napsal(a):
This proposal is just for starting the discussion.
1. Messages contain name=value pairs separated by spaces.
2. All names are just alphanumeric sequences.
3. Values can be either:
a) byte sequences with
a) byte sequences with the following special characters encoded as %XX
where XX is hexadecimal value of the encoded byte. Special characters
are: bytes with value = 0x20 or = 0x7F, '%', '(', ')', and '='.
Perhaps we should reserve more characters for future features - at least
'', '\'' and
On Wed, 2008-03-05 at 10:04 -0500, John Dennis wrote:
a) byte sequences with the following special characters encoded as %XX
where XX is hexadecimal value of the encoded byte. Special characters
are: bytes with value = 0x20 or = 0x7F, '%', '(', ')', and '='.
Perhaps we should reserve more
Hi,
Some of the syscalls provide pointer arguments, but the audit just
provide the pointer value, not the data it pointers to. How can I
retrieve the value the argument pointers to?
Thanks in advance!
--
Linux-audit mailing list
Linux-audit@redhat.com
