cyberskydive 0 #1 September 6, 2001 yeah- this is the UNIX support forums-whats the REAL difference - which do you prefer?Is it just security? What cant I do with SSH?Can you transfer files with either one using STOR?How do I tell it which file I wanna transfer?-LOLCmon UNIX gods - Sun Solaris if that matters.C-28534http://www.sunraydesigns.com Quote Share this post Link to post Share on other sites
Zennie 0 #2 September 6, 2001 We use SSH a lot. AFAIK, the main diff is security.For moving files, use SCP. --------Zennie"I know the pieces fit. 'Cause I watched them fall away..."--Tool Quote Share this post Link to post Share on other sites
fred 0 #3 September 6, 2001 Telnet is bad. If I run a sniffer on your network, or any pc/router between you and your destination, I can read everything you type in telnet, including passwords.ssh is encrypted, so a sniffer does me no good. It's tough to break, and even has some little precautions to stop "man in the middle" attacks.Telnet has no support for transferring files. You need ftp for that. ftp is not secure, either.scp on the other hand, uses an encrypted channel, so you can securely copy files across the net. I believe that ssh has some additional features not available in telnet, not the other way around. Quote Share this post Link to post Share on other sites
cyberskydive 0 #4 September 6, 2001 yup I use ftp regularly but just wondered if I could transfer files since I'm learning new shiot ;)I have putty as an ssh client can anyone recommend another?C-28534http://www.sunraydesigns.com Quote Share this post Link to post Share on other sites
Slappie 9 #5 September 6, 2001 putty is one of the best... I really haven't used anyothers though.My New Website with 24hr Chat Quote Share this post Link to post Share on other sites
MarkM 0 #6 September 6, 2001 SSH uses encryption on the data stream so your session can't be snooped. It also checks keys between hosts and will warn you if the target machine has been switched.The best feature of SSH though is that it'll encapsulate your X windows protocol stream.Not a big deal if you're on windows, but going Unix to Unix it means I can run remote graphical applications locally even through a firewall. Quote Share this post Link to post Share on other sites
DZBone 0 #7 September 6, 2001 What they said. In addition to tunelling X Windows, you can set up tunnels for any other listening port (on either side, any machine that either side can see). I use this to access servers at work from home though the NAT/firewall.As far as clients go, puTTY is OK, but I like TeraTerm with the ssh mods better. My favorite, tho, is OpenSSH. There is a nice Windows port of it available as part of the most excellent Cygwin package. If you are a Unix person stuck in a Windows world, you owe it to yourself to install these tools. It contains basically all of the GNU stuff and more, ported to Winblows.Carl Quote Share this post Link to post Share on other sites
fonz 0 #8 September 10, 2001 cyberskydive> yeah- this is the UNIX support forumsAnd I was thinking I was the only nerd here :-)The main difference between SSH and telnet is security.SSH sessions are encrypted. This means that if somebody is snoopingyour session (something that every annoying moron with your averagescript-kiddie hacking kit can do), he/she/it won't be able to make anysense of it. If you use plain telnet, everything goes over in the open.This includes usernames, passwords and other sensitive information.So, snoopers will be able to intercept your username and password andabuse it as they see fit.I'm not sure if SSH has eavesdropping protection or not.For copying files, use scp or sftp. These are encrypted versions of rcpand ftp respectively.Mind you, though, that telnet isn't all bad.Many servers run daemons that you can communicate with, simply bysetting up a socket connection to a specific port. Instead of writing a Cprogram to do that, you can simply use telnet to connect to that port.The problem with SSH in this case is that in order for SSH to work, bothparties must be able to handle the encryption. For some services likeremote login, encryption makes a lot of sense because sensitiveinformation (e.g. passwords) is involved. But there are a lot of servicesout there that don't support encryption.For example: I have no direct login access to the machine that acts asour news server. But I can (legitimately!) use telnet to connect to thatmachine on the usenet port. Then, I can query the machine e.g. aboutwhich newsgroups it feeds. I have to use telnet for this, because thenews server isn't capable of encrypting the session. But since I'm notrequesting or supplying any sensitive information, this is not a problem.Another example: by telnetting to the mail port of the mailserver, I cansend and read e-mail without an e-mail client (e.g. mutt or elm). All I needis telnet. However, I never do this because the mailserver requiresauthentication (username and password) but doesn't support encryption.Wow, this message is getting way too long.Blue skies and sorry to bore you,Alphons Quote Share this post Link to post Share on other sites
fred 0 #9 September 11, 2001 Quoteby telnetting to the mail port of the mailserver, I cansend and read e-mail without an e-mail client.Do you also surf the web by telnetting to port 80?But you're right. Telnet has its uses when it comes to troubleshooting. Quote Share this post Link to post Share on other sites