similar to: [Bug 920] Enable client multiplexing to fall back to enhance transparency

http://bugzilla.mindrot.org/show_bug.cgi?id=920 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #705 is|0 |1 obsolete| | ------- Additional Comments From djm at mindrot.org 2005-06-03 12:55 -------

This allows me to set 'ControlPath ~/.ssh/sockets/%h.%p.%u' for example. Have I missed a good reason why ssh_connect finds the default port number for itself instead of just having it in options.port (like we do for the the default in options.user)? --- openssh-4.1p1/ssh.c~ 2005-06-12 09:47:18.000000000 +0100 +++ openssh-4.1p1/ssh.c 2005-06-12 09:40:53.000000000 +0100 @@ -604,6 +604,17

https://bugzilla.mindrot.org/show_bug.cgi?id=1557 Summary: ssh multiplexing does not fall back to new connection when server refuses muxd session Product: Portable OpenSSH Version: -current Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh

https://bugzilla.mindrot.org/show_bug.cgi?id=1517 Summary: ssh ControlMaster process is crashing frequently when multiplexing ssh and scp connections with error 'select: Invalid argument' Product: Portable OpenSSH Version: 5.1p1 Platform: Sparc OS/Version: Solaris Status: NEW

Hi, A user has noticed that X11 forwarding does not appear to work when using session multiplexing. It seems that the DISPLAY environment variable is not getting set in the slave sessions. Any thought? The ~/.ssh/config ib below. Host somehost-master ControlMaster yes ControlPath ~/.ssh/somehost.sock HostbasedAuthentication no HostName somehost Host somehost-slave ControlPath

https://bugzilla.mindrot.org/show_bug.cgi?id=2886 Bug ID: 2886 Summary: ssh-copy-id appears to hang indefinitely when ssh multiplexing is enabled, and it permits passwordless login Product: Portable OpenSSH Version: 6.6p1 Hardware: amd64 OS: Linux Status: NEW

hello ssh list, long time user of openssh, but relatively new to the concept of ssh multiplexing. i'm experiencing some issues and i haven't figured out how to troubleshoot it just yet. would appreciate some help if possible. i'm using ssh as a communications mechanism to pass text file based messages between 2 hosts. There are programs on each side that send and receive these

http://bugzilla.mindrot.org/show_bug.cgi?id=1278 Summary: CYGWIN controlMaster connections don't work. Product: Portable OpenSSH Version: v4.5p1 Platform: ix86 OS/Version: Cygwin on NT/2k Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org

https://bugzilla.mindrot.org/show_bug.cgi?id=2363 Bug ID: 2363 Summary: With multiplexing, a forwarding is kept in the list of active forwardings even when it fails Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5

http://bugzilla.mindrot.org/show_bug.cgi?id=1330 Summary: RFE: 'ControlPersist' support -- automatically fork and leave ControlMaster behind as a d?mon Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component:

Hi, I have sshfs and ssh to my host setup to use the same socket with ControlMaster setting. Now when I try to scp a file to/from my host I see poor transfer speed. Also, a cp-ing a file to the mounted filesystem results in poor throughput. On the other hand, if I don't use the multiplexing, I get very good throughput. Now, my question is, when I multiplex, does the IPQoS get set wrongly for a

Hi, It seems there is a problem regarding ControlMaster and scp'ing a file depending on the current working directory: $ cd ~/Personnel $ scp -o ControlMaster=yes cox.jpg host.local: muxserver_listen bind(): No such file or directory lost connection $ scp -o ControlMaster=no cox.jpg host.local: cox.jpg 100% 222KB 222.1KB/s 00:00 $ cd $ scp -o

https://bugzilla.mindrot.org/show_bug.cgi?id=1758 Summary: client hangs when closing a multiplexed session with \n~. Product: Portable OpenSSH Version: 5.4p1 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: unassigned-bugs

TL;DR: I expect ProxyCommand to have effect in preference to ControlPath. I've just tripped over this one. I have an ssh Host (let us call it "MAIN") with a ControlPath and with ControlMaster=no, from the .ssh/config file. I also have a shell script whose purpose is to hop to a remote host through a port forward, which uses the ProxyCommand option like this: ProxyCommand ssh

Dear Mailing List We are using a ControlMaster with a short ControlPersist to access the bastion host which then gives access to customer hosts. Our Information Security Manager would like to disallow the ControlMaster. His attack scenario is an admin workstation with a compromised root account. An attacker can then use the ControlMaster to trivially get shell access on the bastion host

With 'ControlMaster auto' a stale socket will prevent ssh from being able to connect. It'll try to use the socket, fail, then connect for itself... but will then abort when it can't create its own socket. --- openssh-4.2p1/ssh.c~ 2005-09-05 09:49:31.000000000 +0100 +++ openssh-4.2p1/ssh.c 2005-09-05 09:56:34.000000000 +0100 @@ -1247,7 +1247,11 @@ control_client(const char *path)

This is a better approach to persistent control masters than my previous attempt. Instead of forking before we make the connection, do so only when the original session has closed -- much like the code for '~&' backgrounding already does. My earlier patch for 'ControlPath none' still applies and is required, btw. --- openssh/clientloop.c~ 2005-06-17 03:59:35.000000000 +0100

On 03Nov2017 13:07, Damien Miller <djm at mindrot.org> wrote: >On Fri, 3 Nov 2017, Cameron Simpson wrote: >> TL;DR: I expect ProxyCommand to have effect in preference to >> ControlPath. [...] >> On reflection, of course these are distinct options and that side of >> things isn't, of itself, a bug. However, is there a sane use case for >> using

I am trying to set up port forwarding using the client of a multiplexed connection, but the client is dying. The connection paramaters I am using are as follows: for the master: /usr/bin/ssh -T -n -N -o ControlMaster=yes -o ControlPath=/var/run/autossh/control-%r@%h-%p.sock -o ConnectionAttempts=3 -o BatchMode=yes -o EscapeChar=none -o ExitOnForwardFailure=yes -o ServerAliveInterval=15 -o

Hi All. OpenSSH 4.7 is preparing for release so we are asking for any interested folks to please test a snapshot. The main changes are: * sshd(8) in new installations defaults to SSH Protocol 2 only. Existing installations are unchanged. * The SSH channel window size has been increased, which improves performance on high-BDP networks. * ssh(1) and sshd(8) now preserve MAC