Source: src:openssh Version: 1:7.4p1-7 Severity: minor When using unix socket forwarding, both ssh (with -L) and sshd (with -R) forget to remove the socket path on close.
unix(7) says: > Binding to a socket with a filename creates a socket in the filesystem > that must be deleted by the caller when it is no longer needed (using > unlink(2)). In principle socket forwarding should mimic TCP forwarding: closing a listening socket allows other processes to use that port/path. I understand that StreamLocalBindUnlink might be useful when an ssh server or client process did not exit cleanly, but using it by default would just make any previous listener unreachable. I just can't find a reason for leaving a blocker for future listeners behind.
signature.asc
Description: This is a digitally signed message part.
