The username contains slashes. If I use standard
~/.ssh/sockets/master-%r@%h:%p as the ConfigPath, ssh would complain that
unix_listener: cannot bind to path
~/.ssh/sockets/master-username/which/contains/slash@host_ip:port.s5FLlcqcHkethwd0: No such file or directory.
It seems the slash in the username is interpreted as path seperator.
How could I get around this?