3 ms·
> Speaking as someone who was actually using Unix systems when this happened, the "ssh" command was replacing the rsh command, A different data point: I was al
by kloch 3y ago
> Speaking as someone who was actually using Unix systems when this happened, the "ssh" command was replacing the rsh command,
A different data point: I was also a Unix sysadmin at the time (thought just out of school) and for me ssh replaced telnet and ftp. I never used rsh, rlogin, and rcp except when testing exploits.
- teddyh 3y agoIn my experience, telnet and FTP were used when accessing external resources; when wandering around the local menagerie of machinery, rsh, rlogin and rcp were predominant.
- QuercusMax 3y agoTelnet predates UNIX and came from the late 60s; rsh/rlogin were introduced by BSD in the 80s. So if you were in a BSD-derived system, you might have used rsh/rlogin, but otherwise telnet was the standard. Telnet was also cross-platform; I first used it on VMS.
- linsomniac 3y agoDitto, I had been doing sysadmin as my job for a few years in 1995 and as a component of my job or as a hobby for ~5 years before that. I was decidedly a telnet/ftp guy before ssh, and dabbled a little with "ssltelnet". I mostly avoided rsh and family because I didn't love the security model. SSH was a fantastic improvement at the time, though the whole licensing model interfered with my use for the first several years.
- Accujack 3y agoMy experience as well. Much depends on whether your systems were running BSD-style RPC services.