| 12:32 am on Jul 28, 2003 (gmt 0)|
I just assumed that telnet was now far too insecure and ssh basically has its functionality with added security. using ssh for pine for server mail management and various site maintainance tasks on our remote shared virtual domains.
However that's an amateur perception. Interested in hearing any other differences.
| 12:55 am on Jul 28, 2003 (gmt 0)|
We use telnet on our intranet for all our mvBase work (except for some reporting in web reports)
| 8:31 am on Jul 28, 2003 (gmt 0)|
I don't use that pathetic & slow telnet, I use SSH which is much more secure and putty works great for me :)
| 8:39 am on Jul 28, 2003 (gmt 0)|
i used to use telnet till 2002.
then my server got hacked.
once bitten twice shy!
| 9:24 am on Jul 28, 2003 (gmt 0)|
I use telnet a lot.
to play on MUDs*blush*
| 9:38 am on Jul 28, 2003 (gmt 0)|
Due to security restrictions i've found it hard to find hosting partners that would accept telnet. This started some years back. Now it's all ssh, and even that can be hard to find.
I still use telnet for a few purposes, among them for proxy lynx browsing (UA= lynx but not my IP). I mainly do this for usability testing - SE's as well as disabled.
| 2:49 pm on Jul 28, 2003 (gmt 0)|
The advantages of SSH is that
1) It has the functionalities of Telnet
2) It is more secure than Telnet
3) You can use an SSH-based FTP client on the SSH port, which means less configuration and more security :)
| 3:35 pm on Jul 28, 2003 (gmt 0)|
telnet www.webmasterworld.com 80
Yah, I use it sometimes, it's more flexible than Perl's HEAD/GET/POST for what I do. I don't think I'll use it to logon to a remote machine instead of SSH though.
| 7:22 pm on Jul 28, 2003 (gmt 0)|
with SSH there is no reason to use it for business.
| 7:48 pm on Jul 28, 2003 (gmt 0)|
It's not something I use often, if ever, but I do have it running on one machine, "just to be safe". :) I have ssh2 installed on that box as a daemon (ssh2d), and I run telnet via inetd. I've been concerned that the ssh2 daemon could crash (probably being paranoid), so I leave telnet enabled...
The whole purpose of adding ssh as a separate daemon was (I admit, I'm paranoid) so that I'd be able to connect and reboot the machine if inetd went down.
It's running Debian, and has never shown any sign of problems, but... better safe than sorry.
I also have a 4097-bit SSH2 key. :)
| 7:52 pm on Jul 28, 2003 (gmt 0)|
First time I started working in a linux environment at an internet company, I asked about telnet to access the servers (like I'd done in college ;) ).
Then, they educated me about SSH, a bit about security, etc. It's been about 4 years now since I've used telnet, and I can't recall the last time I saw a hosting company offering "telnet" without writing it, "telnet/ssh".
Most of the time now, I have to click the "ssh2" option in putty to get it to connect, as well.
| 8:38 pm on Jul 28, 2003 (gmt 0)|
|telnet www.webmasterworld.com 80 |
And don't forget 'telnet mail.server 25' and 'telnet mail.server 110' as well. But for anything other than debugging higher level protocol servers like HTTP and and SMTP, not a chance. I wouldn't install a telnet server daemon on any of my machines, and I don't think any of the ones I use still have them. It's been years.
| 7:30 pm on Aug 1, 2003 (gmt 0)|
And don't forget 'telnet mail.server 25' and 'telnet mail.server 110' as well.
People may have confused "telnet" service (port 23) with telnet program. The telnet program is a useful program for debugging. But telnet service, IMHO, shouldn't be used any more, even in intranet, your password may be easily sniffered by some young office boys.
| 11:47 pm on Aug 2, 2003 (gmt 0)|
|I don't use that pathetic & slow telnet, I use SSH which is much more secure and putty works great for me |
What's so slow about telnet? I've never seen an ssh implementation that was faster than telnet.
| 5:11 am on Aug 3, 2003 (gmt 0)|
|People may have confused "telnet" service (port 23) with telnet program. |
Well, if the question is about 'telnetd' and 'in.telnetd' (common names for the binary that listens on port 23 to provide shell sessions via the telnet protocol), someone should have said so. I don't use *those*.
| 10:08 am on Aug 4, 2003 (gmt 0)|
I still use telnet. We have a lot of Windows clients, and sometimes I need to connect to my server while working on those - and telnet comes with Windows, even if it is the ****tiest telnet client ever.
Network security isn't an issue, since the connection is one-hop through a switch. A trojan on the client machine is more of a worry, but that could snarf passwords typed into ssh just as easily as ones typed into telnet.