From: Darren Tucker <dtucker@zip.com.au>
To: "David S. Miller" <davem@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, netdev@oss.sgi.com
Subject: Re: [Bugme-new] [Bug 1360] New: Can't access /proc/self/fd/0 from sshd when no pty allocated.
Date: Wed, 22 Oct 2003 18:40:51 +1000 [thread overview]
Message-ID: <3F964293.FA2C3A7A@zip.com.au> (raw)
In-Reply-To: 20031018235735.52f5e15a.davem@redhat.com
"David S. Miller" wrote:
>
> On Sat, 18 Oct 2003 17:27:36 -0700
> Andrew Morton <akpm@osdl.org> wrote:
>
> > This appears to be deliberate:
[snip]
> >
> > I do not know why; the comment is fairly useless.
>
> For many socket types there are no sane open() semantics.
>
> If I open() a unconnected socket, what does that mean?
> Should it connect, of do something like a dup()?
>
> This code has been this way for a long time, anyone who wants to
> change this needs to deal with and address all the aforementioned
> issues.
Thanks for looking at this.
I've done some digging on the OpenSSH side: originally sshd used pipes on
Linux but they were found [0] to have problems that cause lockups in (at
least) rsync.
[0] http://marc.theaimsgroup.com/?l=openssh-unix-dev&m=94914935131492
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
prev parent reply other threads:[~2003-10-22 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200310151142.h9FBgi5k029003@fire-1.osdl.org>
2003-10-19 0:27 ` [Bugme-new] [Bug 1360] New: Can't access /proc/self/fd/0 from sshd when no pty allocated Andrew Morton
2003-10-19 6:57 ` David S. Miller
2003-10-22 8:40 ` Darren Tucker [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=3F964293.FA2C3A7A@zip.com.au \
--to=dtucker@zip.com.au \
--cc=akpm@osdl.org \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.