https://bugzilla.mindrot.org/show_bug.cgi?id=3436
--- Comment #2 from Christoph Anton Mitterer <calestyo@scientia.org> ---
I'm writing a small wrapper tool (which tries to do the wrapping in a
particularly "clean" way) around ssh (and ideally also sftp/scp).
Right now it reads a:
setenv OpenSSHWrapperCommand="something"
(via ssh -G) from ssh_config, and when something comes out of that, it
`eval`s that... otherwise it `exec`s ssh "$@" .
Then I'll add further such commands, specific for ssh, sftp, scp (and
OpenSSHWrapperCommand) just being the "default" for all of them.
If -G were to print out unknown commands (which I've asked for in
another ticket, IIRC) I could directly use a command name for that,
which users would need to add to IgnoreUnknown.
Now there are several possible use cases, basically anything which
needs to be done locally, but for which LocalCommand doesn't suite.
E.g. it might be handy to set up env vars, which are then transmitted
via SendEnv.
Or we have nodes which are reachable via VPN (even with ssh... don't
ask me for the sense in that ^^) ... so the wrapper could initiate that
before.
Obviously it would be even better to have such functionality in ssh
itself, but I guess you'd rather consider it bloat.
But having some help in parsing would still be nice,...
--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
--- Comment #2 from Christoph Anton Mitterer <calestyo@scientia.org> ---
I'm writing a small wrapper tool (which tries to do the wrapping in a
particularly "clean" way) around ssh (and ideally also sftp/scp).
Right now it reads a:
setenv OpenSSHWrapperCommand="something"
(via ssh -G) from ssh_config, and when something comes out of that, it
`eval`s that... otherwise it `exec`s ssh "$@" .
Then I'll add further such commands, specific for ssh, sftp, scp (and
OpenSSHWrapperCommand) just being the "default" for all of them.
If -G were to print out unknown commands (which I've asked for in
another ticket, IIRC) I could directly use a command name for that,
which users would need to add to IgnoreUnknown.
Now there are several possible use cases, basically anything which
needs to be done locally, but for which LocalCommand doesn't suite.
E.g. it might be handy to set up env vars, which are then transmitted
via SendEnv.
Or we have nodes which are reachable via VPN (even with ssh... don't
ask me for the sense in that ^^) ... so the wrapper could initiate that
before.
Obviously it would be even better to have such functionality in ssh
itself, but I guess you'd rather consider it bloat.
But having some help in parsing would still be nice,...
--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs