jury gerold <[EMAIL PROTECTED]> wrote:
> When i create a connection (telnet a.b.c.d port) the signal is
> delivered depending on the user that does the telnet.
> If root creates the socket, then only root or another machine
> is able to trigger the signal by connecting to the socket.
> Normal
On Tue, Sep 12, 2000 at 03:09:40PM +0200, jury gerold wrote:
> Andi Kleen wrote:
> >
> > On Tue, Sep 12, 2000 at 11:33:31AM +0100, Alan Cox wrote:
> > > > > Normal users are only able to create a SIGIO signal when connecting.
> > > >
> > > > That's very unlikely. TCP does not propagate gid/uid in
Andi Kleen wrote:
>
> Never mind I found it.
>
> The patch should fix the problem, could you try it ?
>
> -Andi
It work's now.
Nothing is broken at least on this machine.
That was quick.
2.4.0-x does not have the problem.
Thanks
Gerold
-
To unsubscribe from this list: send the line "unsubsc
Andi Kleen wrote:
>
> On Tue, Sep 12, 2000 at 11:33:31AM +0100, Alan Cox wrote:
> > > > Normal users are only able to create a SIGIO signal when connecting.
> > >
> > > That's very unlikely. TCP does not propagate gid/uid information over sockets,
> > > not even over localhost.
> >
> > However if
> > However if something is looking at current-> and the test is on localhost
> > then it starts to become quite believable
>
> The SIGIO is on the receiving side, not on the sending. current is always
> the same.
Which precisely explains the scenario he is seeing
-
To unsubscribe from this lis
On Tue, Sep 12, 2000 at 11:33:31AM +0100, Alan Cox wrote:
> > > Normal users are only able to create a SIGIO signal when connecting.
> >
> > That's very unlikely. TCP does not propagate gid/uid information over sockets,
> > not even over localhost.
>
> However if something is looking at current-
> > Normal users are only able to create a SIGIO signal when connecting.
>
> That's very unlikely. TCP does not propagate gid/uid information over sockets,
> not even over localhost.
However if something is looking at current-> and the test is on localhost
then it starts to become quite believab
On Tue, Sep 12, 2000 at 02:45:48AM +0200, jury gerold wrote:
> Andi Kleen wrote:
> >
> > On Tue, Sep 12, 2000 at 02:20:02AM +0200, jury gerold wrote:
> > > I ran into a problem with 2.2.x kernels, posix signals and sockets.
> > >
> > > I have a program that creates a serversocket, puts it into li
Andi Kleen wrote:
>
> On Tue, Sep 12, 2000 at 02:20:02AM +0200, jury gerold wrote:
> > I ran into a problem with 2.2.x kernels, posix signals and sockets.
> >
> > I have a program that creates a serversocket, puts it into listen state,
> > attaches the socket to a realtime signal and simply waits
On Tue, Sep 12, 2000 at 02:20:02AM +0200, jury gerold wrote:
> I ran into a problem with 2.2.x kernels, posix signals and sockets.
>
> I have a program that creates a serversocket, puts it into listen state,
> attaches the socket to a realtime signal and simply waits for the signal.
>
> When i c
I ran into a problem with 2.2.x kernels, posix signals and sockets.
I have a program that creates a serversocket, puts it into listen state,
attaches the socket to a realtime signal and simply waits for the signal.
When i create a connection (telnet a.b.c.d port) the signal is delivered dependin
11 matches
Mail list logo
