| Summary: | Please move /tmp/ssh-XXXXXXXXXXXX directory to $XDG_RUNTIME_DIR if set | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Josh Triplett <josh> |
| Component: | ssh-agent | Assignee: | Assigned to nobody <unassigned-bugs> |
| Status: | CLOSED INVALID | ||
| Severity: | normal | CC: | djm |
| Priority: | P2 | ||
| Version: | 5.8p1 | ||
| Hardware: | All | ||
| OS: | All | ||
|
Description
Josh Triplett
2011-04-02 10:50:52 AEDT
/var/run is not user-writable on most Unix variants. Furthermore, safely reaping stale files from /tmp is a long solved problem (In reply to comment #1) > /var/run is not user-writable on most Unix variants. ssh-agent could simply fall back to /tmp if /var/run fails. > Furthermore, > safely reaping stale files from /tmp is a long solved problem Not entirely. Some systems remove old files from /tmp at boot time, but that can result in unexpected data loss. Furthermore, tmpreaper at least avoids removing sockets unless explicitly requested. A correction: this directory should move into $XDG_RUNTIME_DIR if set. That variable will point to a user-writable (and user-specific) directory; if unset, ssh can fall back to $TMPDIR or /tmp as it does now. Recent ssh-agent already honors TMPDIR for this. $XDG_RUNTIME_DIR, when configured, normally points to a user-private directory separate from $TMPDIR. ssh-agent should use $XDG_RUNTIME_DIR in preference to $TMPDIR if set, and fall back to $TMPDIR. close resolved bugs now that openssh-5.9 has been released |