3 ms·
You can disable the access in sshd_config file but, it's enabled out of the box in everything I've used so far. Do you have any examples?
by bayindirh 6y ago
You can disable the access in sshd_config file but, it's enabled out of the box in everything I've used so far.
Do you have any examples?
- sanxiyn 6y agoMany SSH servers do not run OpenSSH. For example, it may run Dropbear, which does not support SFTP.
- shawnz 6y agoDropbear only supports SFTP if you provide the sftp-server binary, same as how it only supports SCP if you provide the scp binary.
- toyg 6y agoThe OpenSSH sshd executable, in absence of a sshd_config, disables it - and rightly so, because you have to specify a server executable to manage it, which may or may not be available. It just so happens most distributions enable it by default. However, a hardened configuration could legitimately disable, to reduce attack space - it's an extra executable where things can go wrong and be exploited. There is also no requirement for non-OpenSSH implementations to have it. To be clear, the problem is not that sftp is unlikely to be available, but that it's possible that it will be the case; hence it does not replace scp in that scenario without complete loss of functionality. It is an objectively inferior option.
- shawnz 6y agoIt's also possible that the scp binary won't be available on the server in just the same way.