| Summary: | ControlPath name collisions when using shared locations like /tmp for the sockets. | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Christoph Anton Mitterer <calestyo> |
| Component: | ssh | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED WONTFIX | ||
| Severity: | enhancement | CC: | djm |
| Priority: | P5 | ||
| Version: | 6.7p1 | ||
| Hardware: | All | ||
| OS: | All | ||
|
Description
Christoph Anton Mitterer
2014-11-15 13:39:14 AEDT
(Sorry, hit enter too fast) This issue is from [0], see also bug #2311. If a shared location like /tmp would be used for the ControlPath setting of ssh, the following issues may arise: 1) %C (the hash hover local host, remote user, hostname, port) alone, may lead to collisions, since local host, remote user, hostname, port are not alone to generate unique names. The local user name should be added to %C. 2) The manpage section which tells people which data they should use at least to prevent collisions should be adapted as well, to also include %u (i.e. the local user name). Cheers, Chris. [0] https://lists.mindrot.org/pipermail/openssh-unix-dev/2014-November/033140.html Like the manual now recommends, don't use shared directories for mux sockets. If you do use shared directories and are happy to accept that particular risk, then it is up to you to make the path unique. You can add %u to the path explicitly very easily. I don't see a compelling reason to change this. (In reply to Damien Miller from comment #2) > I don't see a compelling reason to change this. Becuase it's a better an cleaner way of handling it, for those people who do want to use shared locations, and likely is trivial or doesn't require much work? Apart from that,... same argumentation with the bug #2311 - since closing that one is a mistake, closing this one is either. Close all resolved bugs after 7.3p1 release |