On 20Oct2018 09:14, Cameron Simpson <cs@xxxxxxxxxx> wrote:
and the ssh_config(5) manual entry doesn't mention them.
This looks like an accidental omission.
Want a patch? I'll make one.
I'd like to include the syntactic distinction required, along the
lines of "socket paths are identified by having a leading slash". I'll
check that that's what the code does :-) _If_ that's the criterion,
I'll also offer a patch supporting a leading "./" as well, as it seem
very desirable to me to be able to make the sockets relative to the
users' home directories.
And on reading the code I see that the presence of a slash marks it as a
path and therefore a UNIX domain socket...
Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
_______________________________________________
openssh-unix-dev mailing list
openssh-unix-dev@xxxxxxxxxxx
https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
