Skip to main content

Use SSH-Reject Telenet,RSH/RLogin

The main problem with Telnet/rsh/rlogin/rcp is that they send the information over the wire unencrypted. So whatever you type, your username/passwords that go in clear text over the wire. Anybody can sniff it and make your life difficult. The remote shell utilities such as, rsh, depend on a pre authenticated IP connection. Anything coming from that IP is reliable for them. IP spoofing is not difficult!
So use SSH, Secure way to send information over network.The Secure Shell keeps unauthorized users out of our computers, both by encrypting passwords to protect them from sniffing, and by providing more positive authentication than simple password exchange. Instead of rsh, rcp, and rlogin, simply use the commands ssh, scp, or slogin.
How to tunnel Telnet through SSH:
1. Launch Putty and provide the destination host IP address.
2. Go to SSH->Tunnel.Enter the destination server name or address followed by a colon and the port PuTTY will forward to.


3.Click on the Open button. A terminal window will and prompt you to logon to the remote host using SSH. Enter your name and password to login to the remote host.
4.Now you can connect to this server using any non secure Telnet client. You must note here that you have to connect to the same port which is specified for the destination server in step 2.

Comments

Ritesh said…
SSH tunneling is very useful indeed! It's even easier to set up if you have a Cygwin shell or are using a *nix system.
At the command prompt (cygwin or bash)
# ssh -L 3001:localhost:23 user@domain.com

If you've gone through the trouble of creating a key pair you can get avoid having to enter the password each time you set up the tunnel.

SSH tunneling is even more useful as a tool to bypass restrictive proxies. If you use dynamic tunneling, you can effectively create a SOCKS proxy. For example if you did this:
# ssh -D 8080 user@domain.com

You can now set up your browser to use localhost:8080 as a SOCKS proxy, allowing you to tunnel everything through it. For maximum security you can enable remote DNS lookups in your browser(Firefox has this setting under about:config) so that your browser does not use the default DNS server for name lookups.
August 8, 2011 at 10:44 PM
Post a Comment

Popular posts from this blog

Using an AirPcap device in Windows with Wireshark

Capturing wireless traffic in a Windows environment is unfortunately not as easy as a setting change. As with most Windows-based software, drivers in Windows are often not open source and do not allow for configuration change into monitor mode. With this in mind, we must use a specialized piece of hardware known as an AirPcap device. Once you have obtained an AirPcap device you will be required to install the software on the accompanying CD to your analysis computer. The configurable options include: • Interface - Select the device you are using for your capture here. Some advanced analysis scenarios may require you to use more than one AirPcap device to sniff simultaneously on multiple channels. • Blink LED - Clicking this button will make the LED lights on the AirPcap device blink. This is primarily used to identify the specific adapter you are using if you are using multiple AirPcap devices. • Channel - In this field, you select the channel you want AirPcap to listen on. Extension C...
5 comments
Read more

Anti CSRF header

Recently I came across an application which was preventing crsf attacks using a unique non-traditional approach. In traditional approach the csrf is thwarted by embedding unique random tokens, called nonce, in each sensitive page. But this application, which was making ajax calls and used jQuery, was creating a header to identify the valid and invalid requests altogether. The idea is to generate a custom header, x-session-token in this case, with every request which is considered sensitive and includes any sort of transaction. For example: xhr.setRequestHeader('x-session-token', csrf_token)   At the server level, server checks for this header if found request is fulfilled, otherwise rejected. We need to use xhr calls for making use of this technique, not useful in regular POST and GET requests. Since, I was not aware of this kind of countermeasures, probably, since most of the applications I did were using standard requests. So, I searched a bit and found even Go...
4 comments
Read more

Some one watching where you visited!

Yes... Mozilla has been susceptible to browser-history stealing java script code. Today, Giorgio posted some cool information about the exploit. Mozilla is already working on this. This bug has been reported. Actually they have set up a web site to show the proof-of-concept. Visit www.statrpanic.com in FF,Safari or Netscape and it will tell you which websites have you been already ! But I am not sure it will work in IE or not because my IE is not responding to the website. Clearing history of visited website makes you safe to this attack. I mean this is one way..may be there are other ways to exploit this. But I have found this effective. Try it yourself in FF and then in IE and see the results.
Post a Comment
Read more