4 ms·
I've ported ssh before and I think the whole system is a little hacky. I think what is lacking is a precise split between file transfer and remote command exec
by m463 6y ago
I've ported ssh before and I think the whole system is a little hacky.
I think what is lacking is a precise split between file transfer and remote command execution.
If the split were well defined, we could simply and securely split out file transfer as a "thing".
it would allow:
- write-only no-account-required file uploads
- read-only no-account-required file downloads
- an account-required incoming dropbox
- an account-required file store
- full blown remote filesystems (filestore + file protocol goodies)
and a number of other services that involve files and NOT command execution, environment variables, shells, a login or even a user account.
- fanf2 6y agoDoesn’t the sftp subsystem allow that in principle? You might have to configure the server fairly heavily to make it sftp only, though...
- m463 6y agoIt's been many years, but I vaguely recall there were some things preventing that, but I don't remember if they were protocol or implementation dependent.