https://bugzilla.mindrot.org/show_bug.cgi?id=3609
Damien Miller <d...@mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |d...@mindrot.org --- Comment #1 from Damien Miller <d...@mindrot.org> --- How would this actually work? $RANDOM doesn't end up anywhere usable other than the listening path on the remote side. Do you enumerate all paths there to figure out which one? I suspect $RANDOM isn't the best solution for your underlying problem. For a start, some shells already provide this with syntax that is incompatible with yours (e.g. https://man.openbsd.org/ksh.1#RANDOM). Furthermore, a merely random input is only part of an effective unique/temporary name facility. Would an explicit unique/temporary name facility for forwarded Unix domain sockets be better? There is already an analogous thing for remote-forward ports, where a listener port number of 0 indicates that the server should allocate one and tell the client what it picked. We could do something similar here (say when passed an empty listen pathname). Would this work for you? -- 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