ssh:// Protocol Handler, Updated

Specifically, it seems all arguments to the ssh:// and telnet:// protocol handlers are stripped. While there was never an ssh-specific threat, this seems to be a case of generalized protection against the telnet:// vulnerability.

Fortunately, the work-around is simple. Instead of specifying your login name via the -l option, encode it like so: ssh://<account>@<host>. Thus my prior entry's example would become ssh://wolf@localhost.

It no longer seems possible to specify arbitrary commands to execute (upon successful ssh login), from a stock ssh:// url. Turns out that I never used it anyway, and perhaps now Stefan can breath a little easier...

Saturday, June 19, 2004
01:01 AM