| Summary: | StreamLocalBindUnlink not working | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Harald Hoyer <harald> |
| Component: | ssh | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | NEW --- | ||
| Severity: | enhancement | CC: | benlongo9807, djm, luca, OU4S0YPQ4GIF0BDMXA6HD90Q6ZVEL0, todd.miller |
| Priority: | P5 | ||
| Version: | 7.2p1 | ||
| Hardware: | Other | ||
| OS: | Linux | ||
|
Description
Harald Hoyer
2016-07-21 23:29:03 AEST
Could you take a look at this Todd? ping? A Unix domain socket can be used on either the local or remote side. That is why the StreamLocalBindUnlink and StreamLocalBindMask settings appear in both ssh_config and sshd_config. I'm not sure that overriding the values in sshd_config on the remote end with those from the local ssh is a good idea. Perhaps we need separate options to specify the values to be sent to the remote end? (In reply to Todd C. Miller from comment #3) > A Unix domain socket can be used on either the local or remote side. > That is why the StreamLocalBindUnlink and StreamLocalBindMask > settings appear in both ssh_config and sshd_config. I'm not sure > that overriding the values in sshd_config on the remote end with > those from the local ssh is a good idea. Perhaps we need separate > options to specify the values to be sent to the remote end? why should it be globally restricted in sshd_config? This bug is remarkably irritating! I use domain sockets forwarding to bring my GPG agent with me as I ssh around the universe and roughly 100% of the time, I have to log in, rm the stale forwarding socket, log out, and log back in. "Warning: remote port forwarding failed for listen path /users/nwf/.gnupg/S.gpg-agent" is particularly galling because I have full permission to remove the offending file *and* I have the StreamLocalBindUnlink directive asserted which is documented to solve this problem! There appears to be nothing that executes, server-side, under client control prior to attempting UNIX domain socket bindings, so I can't even hack around the bug with something like .ssh/rc containing a rm call. Just ran into this - the documentation on the client makes it sound like it will clean up the socket when remote forwarding is happening, but the server must be configured to do this. Currently, there is no way to properly do remote forwarding of unix sockets to a server more than once as it will fail the second time. |