1

I'm writing a program in Java using the sockets to communicate with a Telnet server which allows the users to access the file directory in an UNIX OS.

When using Putty to communicate with this server, it prompts me for my username and password, but using my sockets there is nothing from the server except for a string which states that it uses SSH 2.0 - I think.

I'm sure that this has to do with the Telnet protocol, but how do I get the server to ask me for my username and password. What set of commands would I need to give the server in order to access the file directory in an UNIX environment?

Correction: I figured that it's actually using SSH on port 22. It can be accessed using Putty or Microsoft Windows' Telnet program, but it doesn't actually use the Telnet protocol but the SSH protocol.

Keith Layne
  • 3,688
  • 1
  • 24
  • 28
user919860
  • 3,083
  • 4
  • 19
  • 16

3 Answers3

2

SSH isn't telnet. SSH is a protocol that is a lot like telnet, but is encrypted and has a slew of other features. So it looks like youre expecting a plain-text exchange, but what you're getting is the ssh protocol trying to do a handshake.

Telnet runs on port 23, SSH on 22. I imagine you want to use 23. Note: Telnet is old and unencrypetd and dangerous to use over the internet (unless youre going over a VPN or something that encrypts the session).

DrZaiusApeLord
  • 155
  • 1
  • 1
  • 9
  • Actually, I'm trying to use port 22. I had a feeling that I would have to go with ssh and not Telnet, but based on other people's posts, it looks like that suspicion is probably correct. I'm going to have to go study the SSH protocol because I don't think that the server will let me use the UNIX file system using standard Telnet. – user919860 Aug 30 '11 at 14:38
1

There is really nothing to the Telnet protocol for most uses...see this page for details. If the server on the other end is trying to negotiate a SSL connection, which is by far the most likely thing these days, try using a java.net.ssl.SSLSocket instead of a bare TCP socket.

Once you negotiate the connection (see the docs linked above) you should essentially print UNIX CLI commands to the socket and read (& parse) the results. If you just want to access files, maybe use FTP instead. Most modern servers are going to support SFTP.

Edit

With a little poking I found that using SSLSocket directly to connect to a SSH server is cumbersome at best because SSH has its own protocol. You probably don't want to reinvent the wheel on that one. Check out the answers to this question for some pure Java SSH client libraries. You can probably use at least one of these to solve your problem more directly than sending text commands over SSH.

Community
  • 1
  • 1
Keith Layne
  • 3,688
  • 1
  • 24
  • 28
0

Would it be a telnet server, it would be simple.

But what you have is a ssh server, and that is good as it is. telnet is heavily deprecated, as it is not encrypted.

You now have two options: Either use a ssh library or access the ssh command line client (or under Windows: the plink program) via its stdio.

glglgl
  • 89,107
  • 13
  • 149
  • 217
  • Yes. Java maybe has access to `ssh` libraries and is also capable to launch external processes like `plink`. I did the latter in Python and I am sure that it is as well possible in Java. – glglgl Aug 30 '11 at 18:01