Mailing List Archive

[Bug 3449] LocalForward doesn't support ~/path syntax for UNIX sockets
https://bugzilla.mindrot.org/show_bug.cgi?id=3449

Darren Tucker <dtucker@dtucker.net> changed:

What |Removed |Added
----------------------------------------------------------------------------
Blocks| |3418
CC| |dtucker@dtucker.net

--- Comment #1 from Darren Tucker <dtucker@dtucker.net> ---
(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.)


Referenced Bugs:

https://bugzilla.mindrot.org/show_bug.cgi?id=3418
[Bug 3418] tracking bug for openssh-9.1
--
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 3449] LocalForward doesn't support ~/path syntax for UNIX sockets [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=3449

--- Comment #2 from Christoph Anton Mitterer <calestyo@scientia.org> ---
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.

--
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