News for hackers. Stuff that matters.
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by yjftsjthsd-h on Wednesday July 05, 2017 @07:37AM (#14701558)
In the unlikely event that it matters, scp and I believe ssh have a flag to use no encryption.
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by SwellJoe on Wednesday July 05, 2017 @08:11AM (#14701731)
Not that I'm aware of (at least not in openssh; maybe the commercial ssh has such a "feature"). Do you happen to know what that flag is?
Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by simias on Wednesday July 05, 2017 @08:48AM (#14701936)
I'm pretty sure it doesn't have one either, and that's by design. It seems very dangerous to have such an option. The best you can if encryption limits you is to use a faster cypher such as arcfour (RC4).

It actually reminded me of this old OpenSSH poster: http://openbsd.appli.se/images/poster2.jpg

IIRC the "++" on the RSH tombstone is a reference to a config directive that would open RSH access to anybody from anywhere, effectively giving you a very simple and rather inconspicuous way to "trojan" any rsh install. With SSH the best you can do is install a public key in ~/.ssh/authorized_keys, but it's not quite as convenient as simply adding a "++" in a file when nobody's looking.

See for instance https://www.mkssoftware.com/docs/man4/rhosts.4.asp

Re:FreeBSD deprecates all r-cmds (rcp, rlogin, etc.) by yjftsjthsd-h on Thursday July 06, 2017 @05:57PM (#14714280)
Strange; it appears that you're right. There are patches for `-c none`, but nothing official. Perhaps I'm misremembering sibling's suggestion of using a faster cipher.