2017-06-16 18:17 GMT+02:00 Daiki Ueno <dueno@xxxxxxxxxx>: > When forwarding a Unix-domain socket, the remote socket path must be > absolute (otherwise the forwarding fails later). However, guessing > absolute path on the remote end is sometimes not straightforward, > because the file system location may vary for many reasons, including > the system installation, the choices of NFS mount points, or the > remote user ID. You can put a lot into openssh, but isn't this a bit too much? ssh is a transport protocol, and nothing more. Make openssh expanding paths is not the task of the openssh daemons in my opinion. Better would be if you have a session to a remote host, run a script on the reomote host via SSH_MSG_CHANNEL_OPEN and SSH_MSG_CHANNEL_REQUEST to run a command to get the result. The reply should be the path to the socket. Close the I'm working on a sftp client and sftp server for linux, using the same streamlocal method to connect to a socket on the server. This works very nice. Stef Bon the Netherlands _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
