netdev
[Top] [All Lists]

Re: kernel bug in socketpair()

To: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Subject: Re: kernel bug in socketpair()
From: "David S. Miller" <davem@xxxxxxxxxx>
Date: Wed, 23 Jul 2003 08:36:21 -0700
Cc: dgk@xxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, gsf@xxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <1058970007.5520.68.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <200307231332.JAA26197@xxxxxxxxxxxxxxxxxxxxxxx> <1058970007.5520.68.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
On 23 Jul 2003 15:20:08 +0100
Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:

> On Mer, 2003-07-23 at 14:32, David Korn wrote:
> > The first problem is that files created with socketpair() are not accessible
> > via /dev/fd/n or /proc/$$/fd/n where n is the file descriptor returned
> > by socketpair().  Note that this is not a problem with pipe().
> 
> This is intentional - sockets do not have an "open" operation currently.

Sure, but we've known this for a long time.

And because we knew, we decided not to add an "open"
method to sockets.  The reason, as I remember it, was
security.

Was it not?

<Prev in Thread] Current Thread [Next in Thread>