Displaying 20 results from an estimated 40000 matches similar to: "[Bug 85] ssh -2 localhost od /bin/ls | true ignore SIGPIPE"
2008 May 09
3
[Bug 85] ssh -2 localhost od /bin/ls | true ignore SIGPIPE
https://bugzilla.mindrot.org/show_bug.cgi?id=85
Damien Miller <djm at mindrot.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |djm at mindrot.org
--- Comment #6 from Damien Miller <djm at mindrot.org> 2008-05-09 14:41:19 ---
The
2006 Dec 27
0
[Bug 85] ssh -2 localhost od /bin/ls | true ignore SIGPIPE
http://bugzilla.mindrot.org/show_bug.cgi?id=85
------- Comment #5 from jon at stimmel.net 2006-12-28 04:24 -------
I am running into this as well, and have not found a workaround.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2006 Jun 21
0
[Bug 85] ssh -2 localhost od /bin/ls | true ignore SIGPIPE
http://bugzilla.mindrot.org/show_bug.cgi?id=85
chris at ex-parrot.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |chris at ex-parrot.com
------- Comment #4 from chris at ex-parrot.com 2006-06-22 08:50 -------
I see this bug has now been open for
2000 Dec 11
1
OpenSSH 2.3.0p1: Broken pipe / SIGPIPE
Dear OpenSSH gurus! ;-)
I recently upgraded from "OpenSSH 2.1.1p4" to "OpenSSH 2.3.0p1"
on my Linux 2.2.17 box with OpenSSL 0.9.5a (RedHat 7.0).
According to the "ChangeLog", there was a change in SIGPIPE
handling:
| 20000930
| [...]
| - (djm) Ignore SIGPIPEs from serverloop to child. Fixes crashes with
| very short lived X connections. Bug report from
2018 Dec 01
1
[nbdkit PATCH] sh: Don't let child inherit SIGPIPE ignored
While nbdkit itself must run with SIGPIPE ignored, many applications
expect to inherit SIGPIPE in the default state. What's worse, POSIX
states that a non-interactive shell script cannot use 'trap' to
undo an inherited SIG_IGN on SIGPIPE. I have seen several bug
reports over the years of something that works for a developer but
fails under a CI environment, where the root cause was
2001 May 21
1
ignoring SIGPIPE causing problems in pipes
Hi. I'm writing an article on network backups, and instead of using
my old ssh1 software, I decided to go with openssh all the way. I got
the hang of the openssh way of doing protocol 2 public key
authentication, but ssh is failing to terminate when a pipe is broken.
I am ssh-ing to a remote host and doing a cat or zcat of a dump file,
then on the localhost, I'm using restore to extract
2023 Aug 22
0
[RFC PATCH v1 1/2] vsock: send SIGPIPE on write to shutdowned socket
On Mon, Aug 14, 2023 at 10:46:05PM +0300, Arseniy Krasnov wrote:
>
>
>On 04.08.2023 17:28, Stefano Garzarella wrote:
>> On Fri, Aug 04, 2023 at 03:46:47PM +0300, Arseniy Krasnov wrote:
>>> Hi Stefano,
>>>
>>> On 02.08.2023 10:46, Stefano Garzarella wrote:
>>>> On Tue, Aug 01, 2023 at 05:17:26PM +0300, Arseniy Krasnov wrote:
>>>>>
2023 Aug 04
0
[RFC PATCH v1 1/2] vsock: send SIGPIPE on write to shutdowned socket
On Fri, Aug 04, 2023 at 03:46:47PM +0300, Arseniy Krasnov wrote:
>Hi Stefano,
>
>On 02.08.2023 10:46, Stefano Garzarella wrote:
>> On Tue, Aug 01, 2023 at 05:17:26PM +0300, Arseniy Krasnov wrote:
>>> POSIX requires to send SIGPIPE on write to SOCK_STREAM socket which was
>>> shutdowned with SHUT_WR flag or its peer was shutdowned with SHUT_RD
>>> flag.
2023 Aug 04
0
[RFC PATCH v1 1/2] vsock: send SIGPIPE on write to shutdowned socket
On Fri, Aug 04, 2023 at 05:34:20PM +0300, Arseniy Krasnov wrote:
>
>
>On 04.08.2023 17:28, Stefano Garzarella wrote:
>> On Fri, Aug 04, 2023 at 03:46:47PM +0300, Arseniy Krasnov wrote:
>>> Hi Stefano,
>>>
>>> On 02.08.2023 10:46, Stefano Garzarella wrote:
>>>> On Tue, Aug 01, 2023 at 05:17:26PM +0300, Arseniy Krasnov wrote:
>>>>>
2001 Jun 08
0
SSH / X11 auth: needless complexity -> security problems?
On Wed, 6 Jun 2001, Markus Friedl posted the following to Bugtraq:
> this feature [placing the X11 cookie file in /tmp] was inherited
> from ossh and the reason was:
> 1) if $HOME is on NFS, then the cookie travels unencrypted
> over the network, this defeats the purpose of X11-fwding
> 2) $HOME/.Xauthority gets polluted with temorary cookies.
> however,
2023 Aug 22
0
[RFC PATCH v1 1/2] vsock: send SIGPIPE on write to shutdowned socket
On Mon, Aug 14, 2023 at 10:40:17PM +0300, Arseniy Krasnov wrote:
>
>
>On 04.08.2023 18:02, Stefano Garzarella wrote:
>> On Fri, Aug 04, 2023 at 05:34:20PM +0300, Arseniy Krasnov wrote:
>>>
>>>
>>> On 04.08.2023 17:28, Stefano Garzarella wrote:
>>>> On Fri, Aug 04, 2023 at 03:46:47PM +0300, Arseniy Krasnov wrote:
>>>>> Hi Stefano,
2003 Feb 03
8
[Bug 413] Port forwarding: [localhost:]localport:remotehost:remoteport
http://bugzilla.mindrot.org/show_bug.cgi?id=413
markus at openbsd.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
------- Additional Comments From markus at openbsd.org 2003-02-03 19:50 -------
i'll look into this.
------- You are
2002 Nov 28
0
[Bug 448] ssh ignores key specified with -i if agent is running
http://bugzilla.mindrot.org/show_bug.cgi?id=448
markus at openbsd.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|trivial |enhancement
------- Additional Comments From markus at openbsd.org 2002-11-28 21:37 -------
having -i automagically turning off the
2009 Jun 25
0
ignoring SIGPIPE signal + error loading lapack routines
Dear list
I don't know whether this is the right place to post this message. If not,
please redirect me to the proper place.
i have a Perl application on Linux that uses R (V2.9.0) through the Perl-R
interface.
basically, the application performs statistical analysis using R, and
displays the R output (JPG image of the particular analysis) to the user.
in general, this works fine. but i
2019 Dec 06
0
Error in close.connection(p) : ignoring SIGPIPE signal
Hi Benjamin,
you cannot pipe to echo, since it does not read from stdin.
echo just echos is first arg, i.e. echo /dev/stdin > /dev/null will echo the string "/dev/stdin"to /dev/stdout, which is redirected to /dev/null.
Try
p <- pipe("cat > /dev/null", open = "w")
instead.
Regards,
Andreas
2019-12-06 02:46 GMT+01:00 Benjamin Tyner<btyner at
2002 Nov 21
3
[Bug 413] Port forwarding: [localhost:]localport:remotehost:remoteport
http://bugzilla.mindrot.org/show_bug.cgi?id=413
markus at openbsd.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sjc at makalumedia.com
------- Additional Comments From markus at openbsd.org 2002-11-22 09:48 -------
*** Bug 441 has been marked as
1998 Sep 01
0
SOLARIS:SIGPIPE in nmbd (PR#8723)
appro@fy.chalmers.se wrote:
>
> No, it's not:-)
>
> static int sig_pipe(void)
> {
> BlockSignals( True, SIGPIPE );
>
> DEBUG( 0, ("Got SIGPIPE\n") );
> if ( !is_daemon )
> exit(1);
> BlockSignals( False, SIGPIPE );
> #ifndef DONT_REINSTALL_SIG
>
2001 Oct 10
0
ssh hangs instead of exiting
On Mon, 8 Oct 2001, Markus Friedl wrote:
> Date: Mon, 8 Oct 2001 23:12:41 +0200
> From: Markus Friedl <markus at openbsd.org>
> To: Ed Phillips <ed at UDel.Edu>
> Subject: Re: ssh hangs instead of exiting
>
> On Mon, Oct 08, 2001 at 05:07:12PM -0400, Ed Phillips wrote:
> > On Mon, 8 Oct 2001, Markus Friedl wrote:
> >
> > > Date: Mon, 8 Oct 2001
2002 May 28
2
rsync 2.5.4 (probably 2.5.5 too) server handles SIGPIPE very poorly
(I am not on the rsync mailing list, so if you send a response to this
message to the list, please be sure to CC me.)
I first reported this bug go Red Hat in
<URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=65350>.
If you run rsync with a subshell through ssh.com's ssh and sshd and
then kill the client with ctrl-C, the rsync server process running on
the remote machine grows
2019 Dec 06
2
Error in close.connection(p) : ignoring SIGPIPE signal
Not sure if this is a bug, so posting here first. If I run:
?? cnt <- 0L
?? while (TRUE) {
? ? ?? cnt <- cnt + 1L
? ? ?? p <- pipe("echo /dev/stdin > /dev/null", open = "w")
? ? ?? writeLines("foobar", p)
? ? ?? tryCatch(close(p), error = function(e) { print(cnt); stop(e)})
?? }
then once cnt gets to around 650, it fails with:
?? [1] 654
??