Thanks!
Just for documentation in case anyone gets stuck trying to fix this:
It looks like older FC4 pam will work with ^30, and newer (pam-0.79-9.6)
requires *both* ^29 and ^30. (Doesn't matter, BTW, whether you have
pam_loginuid.so in your config, it looks like it is patched to use audit
r
Quoting Herbert Poetzl ([EMAIL PROTECTED]):
> ah, you are the one who is to blame for this mess ... :)
Well, I wanted to use lsm hooks, not capabilities...
> > For vserver, loginuid should probably always be reported along with
> > the vserver id, I guess...
>
> patches to virtualize the loginui
On Mon, Nov 14, 2005 at 06:54:23AM -0600, Serge E. Hallyn wrote:
> Quoting Gregory (Grisha) Trubetskoy ([EMAIL PROTECTED]):
> >
> > On Thu, 14 Jul 2005, Enrico Scholz wrote:
> >
> > >[EMAIL PROTECTED] (Enrico Scholz) writes:
> > >
> > >>| # auditctl -m 'foo'
> > >>| Error sending user message req
Quoting Gregory (Grisha) Trubetskoy ([EMAIL PROTECTED]):
>
> On Thu, 14 Jul 2005, Enrico Scholz wrote:
>
> >[EMAIL PROTECTED] (Enrico Scholz) writes:
> >
> >>| # auditctl -m 'foo'
> >>| Error sending user message request (Operation not permitted)
> >>...
> >>This gives problems on Fedora Core 4 a
On Thu, 14 Jul 2005, Enrico Scholz wrote:
[EMAIL PROTECTED] (Enrico Scholz) writes:
| # auditctl -m 'foo'
| Error sending user message request (Operation not permitted)
...
This gives problems on Fedora Core 4 as recent pam upgrade is
using this functionality and most actions (su, cron) will
On Sun, Jul 17, 2005 at 01:52:49PM +0200, Enrico Scholz wrote:
> [EMAIL PROTECTED] (Herbert Poetzl) writes:
>
> >> > it seems to be impossible to use the audit (CONFIG_AUDIT) interface
> >> > of the kernel within a vserver:
> >> >
> >> > | # auditctl -m 'foo'
> >> > | Error sending user message r
[EMAIL PROTECTED] (Herbert Poetzl) writes:
>> > it seems to be impossible to use the audit (CONFIG_AUDIT) interface
>> > of the kernel within a vserver:
>> >
>> > | # auditctl -m 'foo'
>> > | Error sending user message request (Operation not permitted)
>> > ...
>> > This gives problems on Fedora
* Herbert Poetzl ([EMAIL PROTECTED]) wrote:
> hmm, does anybody know why pam would want to do syscall
> auditing in the first place? I'm a little lost here
> actually ...
Pam sets up the auid for each login session. This requires
CAP_AUDIT_WRITE. The auid is then used in any messages generated
v
On Fri, Jul 15, 2005 at 12:50:51AM +0200, Herbert Poetzl wrote:
> On Thu, Jul 14, 2005 at 03:21:36PM +0200, Enrico Scholz wrote:
> > Hello,
> >
> > it seems to be impossible to use the audit (CONFIG_AUDIT) interface
> > of the kernel within a vserver:
> >
> > | # auditctl -m 'foo'
> > | Error sen
On Thu, Jul 14, 2005 at 03:21:36PM +0200, Enrico Scholz wrote:
> Hello,
>
> it seems to be impossible to use the audit (CONFIG_AUDIT) interface
> of the kernel within a vserver:
>
> | # auditctl -m 'foo'
> | Error sending user message request (Operation not permitted)
>
> The generated syscalls
On Thu, Jul 14, 2005 at 05:32:40PM +0200, Enrico Scholz wrote:
> [EMAIL PROTECTED] (Enrico Scholz) writes:
>
> > | # auditctl -m 'foo'
> > | Error sending user message request (Operation not permitted)
> > ...
> > This gives problems on Fedora Core 4 as recent pam upgrade is
> > using this functio
[EMAIL PROTECTED] (Enrico Scholz) writes:
> | # auditctl -m 'foo'
> | Error sending user message request (Operation not permitted)
> ...
> This gives problems on Fedora Core 4 as recent pam upgrade is
> using this functionality and most actions (su, cron) will fail
> therefore.
Quick workaround i
Hello,
it seems to be impossible to use the audit (CONFIG_AUDIT) interface
of the kernel within a vserver:
| # auditctl -m 'foo'
| Error sending user message request (Operation not permitted)
The generated syscalls are:
| socket(PF_NETLINK, SOCK_RAW, 9) = 3
| fcntl64(3, F_SETFD, FD_CLOE
13 matches
Mail list logo
