Do you have a clone of the previous OS? Copy it back to /usr/bin, otherwise it’s gone as you noticed. There was an old thread in this forum about it.So I just found out telnet does not work from terminal anymore. I have some devices that is not ssh friendly. Anyone have a solution?
I have a Time Machine back up of Sierra, will try to copy it.Do you have a clone of the previous OS? Copy it back to /usr/bin, otherwise it’s gone as you noticed. There was an old thread in this forum about it.
Use a telnet app.So I just found out telnet does not work from terminal anymore. I have some devices that is not ssh friendly. Anyone have a solution?
So I just found out telnet does not work from terminal anymore. I have some devices that is not ssh friendly. Anyone have a solution?
For telnet, you can probably just use nc (netcat) instead.
Code:nc <hostname> <port>
try this:Confirmed. Star Wars no longer plays
telnet towel.blinkenlights.nl
nc towel.blinkenlights.nl 23
This is annoying; telnet is still used by system administrators quite a bit.
Is Apple losing touch? Certainly feels like it lately.
Well besides dropping programs bash, rysnc and others are just ancient. I understand Apple's rationale for not updating them. But at this point it is getting pretty ridiculous how out of date things are. Part of the attraction of a Mac for me was being *nix system. But if the tools are older than Windows Vista that is pretty sad.
It doesn't matter how ancient telnet is; it hasn't changed in 20 years. It just makes a TCP connection to a port on a remote host.
Some software is incredibly mature and does not need to be updated. It does the job perfectly and doesn't need additional features.
As for rsync, it's still very much being maintained, and is still incredibly useful with functionality being added for greater performance and reliability. We use it at our site for remote backups. It's Apple's fault that they're still using such an old version.
This is annoying; telnet is still used by system administrators quite a bit.
Is Apple losing touch? Certainly feels like it lately.
If you're a system administrator and your corporate network uses Telnet, you now have one more excuse to tell the executives on why they should disable telnet and upgrade to SSH.
And if you're a system administrator and you can't find an easy workaround to this problem, well, you are not a very good system administrator.
If you're a system administrator and your corporate network uses Telnet, you now have one more excuse to tell the executives on why they should disable telnet and upgrade to SSH.
And if you're a system administrator and you can't find an easy workaround to this problem, well, you are not a very good system administrator.
Like I said in post #7, you can use netcat instead of the telnet client. Telnet is an old, outdated, deprecated protocol that passes the entire communication (including credentials) in plaintext. You should not be using it. But if you have to, you can install it separately or just use netcat.There are plenty of network devices (switches, printers, IP cameras, and other gear) that still use telnet for configuration. Educate thyself before you make assumptions about why system administrators need telnet.
There are plenty of network devices (switches, printers, IP cameras, and other gear) that still use telnet for configuration. Educate thyself before you make assumptions about why system administrators need telnet.
And yes, we can SSH to some Linux system on the network and telnet from there. But it's silly to remove something so tiny from the OS that is still used regularly across the industry.