i just noticed that the env. variable SSH_ORIGINAL_COMMAND is no more set if there is no forced command. was there a reason to do so? Background: I'm using a wrapper that can be used as forced command and as shell. (most of the time as forced command, but now I had a task where it had to be used as shell) The wrapper currently only gets its parameters by parsing the SSH_ORIGINAL_COMMAND variable and ignores anything after the -c option. This worked when I implemented it (OpenSSH 2.9). Frank
Apparently Analagous Threads
- 'command' option in authorized_keys
- Make SSH_ORIGINAL_COMMAND available in AuthorizedKeysCommand context
- Subsystem sftp invoked even though forced command created
- [Bug 2253] New: No "$@"-like SSH_ORIGINAL_COMMAND leads to escaping, arg-sep and metachar issues
- Subsystem sftp invoked even though forced command created