From: Jeff Hansen <x@jeffhansen.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 1/1] net/unix: Allow Unix sockets to be treated like normal files
Date: Wed, 27 Oct 2010 20:50:17 -0600 [thread overview]
Message-ID: <4CC8E4E9.2060209@jeffhansen.com> (raw)
In-Reply-To: <20101027.193212.193709254.davem@davemloft.net>
Dave,
I agree that on larger systems this doesn't really make sense, but on
embedded platforms this can save some code space since applications can
get rid of their FIFO listeners and have strictly socket listeners.
That's why I made it an option that could be disabled by default.
Do you know who originally suggested that "creepy crawlies" are
introduced by allowing sockets to be opened? I'd be interested to know
how this could affect security, if at all.
-Jeff
On 10/27/2010 08:32 PM, David Miller wrote:
> From: x@jeffhansen.com
> Date: Thu, 28 Oct 2010 02:24:29 +0000
>
>> Resent. Is there anything else I need to do for this patch to get reviewed
>> and/or merged? Any comments by anyone?
> I don't like this idea at all.
>
> I remember there is a reason why similar things are not allowed for
> sockets, it causes all sorts of problems although I forget the exact
> details.
>
> Take a look at net/socket.c:sock_no_open(), for example.
>
--
---------------------------------------------------
"If someone's gotta do it, it might as well be me."
x@jeffhansen.com
prev parent reply other threads:[~2010-10-28 2:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 2:24 [PATCH 1/1] net/unix: Allow Unix sockets to be treated like normal files x
2010-10-28 2:32 ` David Miller
2010-10-28 2:50 ` Jeff Hansen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CC8E4E9.2060209@jeffhansen.com \
--to=x@jeffhansen.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).