| Summary: | /tmp/ssh-xxxx socket directories clutter up /tmp | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Peter Simons <simons> |
| Component: | ssh-agent | Assignee: | OpenSSH Bugzilla mailing list <openssh-bugs> |
| Status: | CLOSED WONTFIX | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | -current | ||
| Hardware: | Other | ||
| OS: | Other | ||
|
Description
Peter Simons
2002-06-25 18:50:21 AEST
/tmp is the most portable world-writable location. as to hiding them with dot, i just don't see strong justification for this. Is there any strong justification for _not_ hiding them with a dot? Or could you add a configure option (or run-time configure option) that let's me change this without having to patch the source code? Because you end up with worthless options and feature creep. There are too many options as it is right now. Changing the name of the /tmp/ssh-xxxx directory to /tmp/.ssh-xxx won't require any options to be added but it would still solve my problem ... somewhat. Would you please consider doing that then? why is it a problem if they are visible? they should be. apart from this, changing the name might break existing scripts. Well, it is a problem because on a multi-user system there are _hundreds_ of them. And it's not only hundreds of ssh-agent sockets, it's hundreds of Emacs server sockets, ORBit sockets, X11 sockets and so on and so forth. Once the system has been up and running for a few weeks, you cannot possibly read the output from a "ls /tmp" without getting a 23" screen first ... ssh-agent supports the -a option to specify a socket path. Tell you users. Mass change of RESOLVED bugs to CLOSED |