News for hackers. Stuff that matters.
Re:Deprecating scp by VLM on Friday November 06, 2020 @09:17AM (#25007714)
Note that the contents of /etc/ssh/sshd_config are USUALLY compatible across operating systems.

So you can use ansible to install a common and secure and standardized sshd config across, say, legacy linux and new freebsd servers.

With the tiny little problem that filesystem paths will be different for linux and freebsd.

On modern freebsd, from memory, this sshd config line works:

Subsystem sftp /usr/libexec/sftp-server

I forget the path on legacy linux.

Anyway the simplest and most secure way is just to disable sftp across all systems and just use ssh and scp.

The solution to this problem is likely not to be shipping multiple inevitably slightly incompatible sshd configs, but I'll probably end up shipping exactly and precisely one sshd_config with the path on all operating systems being /usr/local/libexec/sftp-server or something like that, and then ansible rules to symlink freebsd and linux to the "standard" path.

Or I'll go all in on freebsd and get rid of the last legacy linux servers.

Or I'll reduce security by using ansible with multiple sshd_config files.

Or recode everything that used scp to use rsync or other alternatives (LOL as if thats happening)

At any rate as usual with unix there's multiple ways to handle things, which is good. Its not like windows or systemd based operating systems.

Re:Deprecating scp by rkeene2 on Friday November 06, 2020 @11:02AM (#25008578)
Which Linux distributions are you referring to with the "legacy" moniker ?
Re:Deprecating scp by kelnos on Saturday November 07, 2020 @01:46AM (#25013564)
I think the parent has some sort of axe to grind with Linux in general, and believes any Linux-based OS to be "legacy", with FreeBSD as the "obvious" replacement. Clearly the parent lives in a different reality than the rest of us.
Re:Deprecating scp by pseudalopex on Friday November 06, 2020 @05:42PM (#25011839)
"Subsystem sftp internal-sftp" works since OpenSSH 4.9.