openssh bugs - Apr 2005 - [Bug 943] sftp will not send from a named pipe

http://bugzilla.mindrot.org/show_bug.cgi?id=943


djm at mindrot.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




------- Additional Comments From djm at mindrot.org  2005-04-21 18:34 -------
Actually, we can't apply this patch: it is impossible to tell if there is a
process on the other end of a fifo and reads will hang if there is none. We are
already hit by this bug in scp (see bug #856).





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=943


mark.fuller at earthlink.net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |




------- Additional Comments From mark.fuller at earthlink.net  2005-04-22 01:09
-------
I strongly disagree. According to your logic nothing can legitimately read or
write a FIFO because it's every reader/writer's responsbility for the
other end
of the pipe? You've just pronounced FIFOs unuseable by *anybody*?

In fact, I use Expect to drive sftp and I set my own criteria for timing out the
operation. Why is this a bad solution? If you're concerned someone will use
a
FIFO without understanding what the ramifications are, why not default it to
non-support and allow users to pass a parm enabling the support?

Thanks,
Mark



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.