On Tue, 30 Aug 2016, Darren Tucker wrote: > On Tue, Aug 30, 2016 at 7:08 AM, Aris Adamantiadis <aris@xxxxxxxxxxxx> wrote: > > Why "ExecRemoteCommand" > > Probably defaults to yes with "ExecRemoteCommand no" to act like -N. > > If we're going to do this (and I'm not sure about it) then maybe we > could do it via the proposed RemoteCommand [0] option as > "RemoteCommand none" rather than another option. Not sure that would work, as there are three states that are possible: login: ssh example.com command: ssh example.com command don't run a command ssh -N example.com Maybe a multi-state RemoteCommand $command | none | don't (better name wanted). But I'm also ambivalent about a RemoteCommand option too... -d _______________________________________________ openssh-unix-dev mailing list openssh-unix-dev@xxxxxxxxxxx https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev
