Bug#569018: openssh-client: recreate mux control socket

2010-09-24 Thread Andrew O. Shadoura
tags 569018 + fixed-upstream -- Hello. The bug is fixed by recent upstream commit: --- Comment #1 from Damien Miller 2010-09-24 22:20:14 EST OpenSSH -current now atomically establishes a listening mux master socket at the specified location, so a client encountering a mux master socket that ref

Bug#569018: openssh-client: recreate mux control socket

2010-03-29 Thread Andrew O. Shadoura
Hello Colin. On Tuesday 09 February 2010 18:22:45 Colin Watson wrote: > (Also, it would be best for this to go upstream to bugzilla.mindrot.org. > I can proxy for you if you like, but sometimes it's both better and > quicker for upstream to be able to discuss the patch directly with the > author r

Bug#569018: openssh-client: recreate mux control socket

2010-02-09 Thread Andrew O. Shadoura
On Tuesday 09 February 2010 18:22:45 Colin Watson wrote: > On Tue, Feb 09, 2010 at 02:45:41PM +0200, Andrew O. Shadoura wrote: > > This patch enables re-creation of the control socket for multiplexing. > > Without it, if ssh dies, it leaves socket in place, and newly started ssh > > cannot bind to

Bug#569018: openssh-client: recreate mux control socket

2010-02-09 Thread Colin Watson
On Tue, Feb 09, 2010 at 02:45:41PM +0200, Andrew O. Shadoura wrote: > This patch enables re-creation of the control socket for multiplexing. > Without > it, if ssh dies, it leaves socket in place, and newly started ssh cannot bind > to it. Thanks for your patch. This has certainly long been an

Bug#569018: openssh-client: recreate mux control socket

2010-02-09 Thread Andrew O. Shadoura
Package: openssh-client Version: 1:5.3p1-1 Hello. This patch enables re-creation of the control socket for multiplexing. Without it, if ssh dies, it leaves socket in place, and newly started ssh cannot bind to it. -- WBR, Andrew --- openssh-5.3p1.orig/mux.c 2010-02-09 14:35:32.0 +0200