SOLVED, I think. The answer, apparently, is to make the path to the wrapper script suggested by Catalin Patulea (see below) the value of the exported environment variable AUTOSSH_PATH prior to calling autossh.
On 10/04/2013 09:02 PM, Catalin Patulea wrote: > You could always write a small wrapper script that adds whatever > command-line arguments you need, and pass *that* to autossh. > > #!/bin/sh > exec path/to/dropbear -y "$@" > > On Fri, Oct 4, 2013 at 12:31 PM, Steve Newcomb <[email protected]> wrote: >> I'm using OpenWRT. My router, whose IP address changes unpredictably, >> makes its ssh-listening port available on another host running at a >> stable IP address, using autossh/dropbear to create a reverse channel. >> >> Sometimes the host's key changes from time to time, which can stop the >> autossh process at a prompt (to nobody) to decide what to do about the >> change. >> >> Ordinary OpenSSH has a StrictHostKeyChecking option which can be used to >> bypass the so-called "ask" prompt and just make the connection regardless. >> >> By reading the source, I learned that Dropbear's ssh client evidently >> has a similar feature, the "-y" invocation option. But I can't pass the >> -y to it via autossh because autossh doesn't approve of it. Dropbear's >> ssh client also does not offer a config file utility, AFAIK. >> Dropbear evidently ignores all -o options, too; they wind up in a bit >> bucket called something like "dummy". >> >> Does anybody know the answer, short of editing/recompiling autossh so it >> won't be so persnickety and just get out of the way? >> >> Steve Newcomb
