Using –/.ssh/authorized keys to decide what the incoming connection can do
dan.langille.org
dan.langille.org
I created a shell script on the second host called "from_host_1" which implements the logic to parse the first host's request and any file paths it supplies, validates them, translates the paths as needed, and then executes the corresponding program.
This way, I can just use a single SSH key which can perform multiple functions. On the first host, I have a bunch of tiny scripts like `~/bin/func` which basically performs `ssh secondhost func "$@"`.
In the OPs case, they seem to have two different hosts which can run two different commands. Two separate SSH keys seems like a reasonable thing to do, because sharing the same key across two systems increases your risk if one machine is compromised.
There is a whole lot that SSH can do that most people don't know about.
I had to port ssh to embedded hardware decades ago, and pulling back the curtains I came to the opinion that everything was a mess.
for example, I needed to be able to upload/download firmware, and was surprised to find that scp wasn't a pure file transfer protocol. It is more like "log into the remote system via shell and run a file transfer program"
There are lots of other things I didn't like, like wholesale transferring environment variables back and forth, weird shell interactions and more.
It is very useful, but it is an organically grown program, not a designed protocol.
Just take a step back and think what you could do if it were a protocol:
- limit visible files
- limit access to files by user
- make access strictly read-only
- allow upload-only (sort of a dropbox)
- clear separation between login access and file access
- remove login user from the whole mess
- trivially tie in as a filesystem.
etc...
default
access none /dev /sys /proc
user foo
access ro /var/scp/firmware
access rw /var/scp/user-foo
user anonymous
access w /var/scp/dropbox
user joe
access rw /home/joe
user fred
access rw /
user backup
access ro /Subsystems are pluggable, so you could write your own subsystem that does enforce whatever config and permission model you want. It's not terribly difficult to do, and you can replace the sftp subsystem entirely.
and just a FYI, currently scp is plumbed over the sftp subsystem, so replacing the sftp subsystem would "fix" scp and sftp clients for you.
iOS Shortcuts has the built-in ability to run SSH commands on a remote server, including passphrase-less pubkey auth.
One can easily build a shortcut with a nice-ish user interface to run various commands on the server, which can be locked down to run a specific script that inspects `SSH_ORIGINAL_COMMAND` to determine what to do.
Because this can use a string comparison (without necessarily putting any user input into the command executed), it should help project against risks like shell injection while still allowing some degree of dynamic control (instead of potentially requiring one script and one SSH key per command).