Hey. LocalForward, and presumably the other *Forward options too, doesn't seem to support ~/ syntax for UNIX sockets, as e.g. supported by options like IdentityFile. e.g.: LocalForward ~/.ssh/forward-sockets/foo /home/remote-user/sock doesn't work, while: LocalForward /home/local-user/.ssh/forward-sockets/foo /home/remote-user/sock works. Perhaps that could be added. Thanks, Chris.
(In reply to Christoph Anton Mitterer from comment #0): > LocalForward, and presumably the other *Forward options too, doesn't > seem to support ~/ syntax for UNIX sockets, as e.g. supported by > options like IdentityFile. That would not be hard to add. Note that it would not make sense to expand tildes for the remote path since there's no guarantee that the local path is the same as the remote path (this is not in your example, just mentioning it.)
I guess for a remote expansion sshd would need to support it? At least ssh should then fail (or warn), if a remote component is a tilde-expansion style pathname, so that users don't wrongly assume it might work.