Mailing List Archive

[Bug 3649] Control sockets do not connect anymore (after updating OpenSSH)
https://bugzilla.mindrot.org/show_bug.cgi?id=3649

Damien Miller <djm@mindrot.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org

--- Comment #1 from Damien Miller <djm@mindrot.org> ---
Please attach debug logs (ssh -ddd ...) from both the multiplexing main
and client processes

--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3649] Control sockets do not connect anymore (after updating OpenSSH) [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=3649

--- Comment #2 from wolfgang.liessmann@web.de ---
There is no option '-d', see output below.
Do you mean '-vvv' for increasing the verbosity level?


```
$ ssh -ddd [...]
ssh: illegal option -- d
usage: ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-B bind_interface] [-b
bind_address]
[-c cipher_spec] [-D [bind_address:]port] [-E log_file]
[-e escape_char] [-F configfile] [-I pkcs11] [-i
identity_file]
[-J destination] [-L address] [-l login_name] [-m mac_spec]
[-O ctl_cmd] [-o option] [-P tag] [-p port] [-R address]
[-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]]
destination [command [argument ...]]
ssh [-Q query_option]


$ ssh -d
ssh: illegal option -- d
usage: ssh [-46AaCfGgKkMNnqsTtVvXxYy] [-B bind_interface] [-b
bind_address]
[-c cipher_spec] [-D [bind_address:]port] [-E log_file]
[-e escape_char] [-F configfile] [-I pkcs11] [-i
identity_file]
[-J destination] [-L address] [-l login_name] [-m mac_spec]
[-O ctl_cmd] [-o option] [-P tag] [-p port] [-R address]
[-S ctl_path] [-W host:port] [-w local_tun[:remote_tun]]
destination [command [argument ...]]
ssh [-Q query_option]


$ ssh -V
OpenSSH_9.6p1, OpenSSL 3.2.0 23 Nov 2023
```

--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3649] Control sockets do not connect anymore (after updating OpenSSH) [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=3649

--- Comment #4 from wolfgang.liessmann@web.de ---
Created attachment 3785
--> https://bugzilla.mindrot.org/attachment.cgi?id=3785&action=edit
SSH log (master and client)

--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3649] Control sockets do not connect anymore (after updating OpenSSH) [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=3649

--- Comment #5 from wolfgang.liessmann@web.de ---
Anonymized logs attached (for both master and client).

--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3649] Control sockets do not connect anymore (after updating OpenSSH) [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=3649

--- Comment #6 from Damien Miller <djm@mindrot.org> ---
Comment on attachment 3785
--> https://bugzilla.mindrot.org/attachment.cgi?id=3785
SSH log (master and client)

> debug1: forking to background

unfortunately logs from the mux master process are lost after this
point. Can you reproduce the problem without -f on its commandline? If
so, please try to catch debug logs from it in that state.

I assume both commands are being run in the same directory? Does "ls -l
socket.tmp" show a socket on the filesystem when you run the client?

--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 3649] Control sockets do not connect anymore (after updating OpenSSH) [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=3649

--- Comment #9 from wolfgang.liessmann@web.de ---
Running the master process in the foreground with only 'ssh -vvv -MN -S
socket.tmp host1' (and then the client process in a different terminal)
works well.

But any background execution of the master process (with '-f' and
either '-o ControlPersist=20' or 'ControlPersist=yes') seems to fail
and the process disappears.
There is no ssh process shown in the output of 'ps -ax' (Mac), and
trying to bring it into the foreground with 'fg' fails ('fg: no current
job').

I don't know the previous openssh version. But on the server side it
still says 'OpenSSH_9.2p1, OpenSSL 1.1.1s 1 Nov 2022', maybe this one
worked.

--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs