First, the original questions:
Brian Exelbierd wrote:
> We are considering implementing a secure telnet solution and I was
> curious if anyone here had any caveats or experience? What software did
> you use, both on the client and server side? Did you continue to allow
> unsecured access? Can you restrict logins on certain ids to secure only
> The majority of our clients are utilizing windows 95, and we are looking
> at SecureCRT from Vandyke (www.vandyke.com). We are currently running
> Solaris 2.6, and several other unixes.
Overwhelmingly people recommended the ssh daemon for use.
It is available from ftp.cs.hut.fi/pub/ssh
For commercial use you must purchase through DataFellows.
On the client side the ssh client was endorsed and everyone was very
positive about secure CRT.
Other clients mentioned included:
F-Secure from DataFellows www.datafellows.com (works with Exceed too)
Tera Term Pro
secure shell (ssh) - available http://www.uni-karlsruhe.de/~ig25/ssh-faq/
One caveat is that SecureCRT only supports version 2.0.x of SSH, not version
I got only one policy response:
We do not allow unsecured access to internet machines. Internal machines,
by the nature of who needs to access them, continue to allow insecure
access, but we do not allow the rhost-type services.
Other comments of note:
Hughes sells a product that is flexible enough to do what you want. It's
called Netlock. Sorry no other current info available. I have used the
product in the past, and it works well.
I am looking at SRP (Secure Remote Password) from Stanford University.
SRP Telnet is backward-compatible, i.e. it can connect to an old-style,
plaintext-password telnet server.
I got hold of it only last week, therefore I am not yet able to give more
See <http://srp.stanford.edu/srp> for more information.
Sources are included. Site also has comparison with SSH and other protocols.
I am going to propose the implementation of the SecureCRT with the
DataFellows SSH daemons for our unix boxes. Given our environment, the
elimination of non-encrypted telnet is probably not an option.
Thanks to everyone for the great information:
Auteria Wally Winzer Jr. wally.winzer@ChampUSA.COM
Greg Obremski firstname.lastname@example.org
David L. Markowitz David.Markowitz@litronic.com
Kelly Setzer email@example.com
Cooke, Earl R. COOKEEA@mail.northgrum.com
Swee-Chuan Khoo firstname.lastname@example.org
Patrick Shannon email@example.com
Roy S. Rapoport firstname.lastname@example.org
Timothy Lorenc email@example.com
Justin Clift firstname.lastname@example.org
Ronan MELENNEC MELENNEC_Ronan@cena.dgac.fr
Jim Seavey email@example.com
Graham Leggett firstname.lastname@example.org
Andrew Kyle andrew_kyle@CommerzbankZGE.com
Au , Louis LAu@bridge.com
Robert L. Harris Robert.Harris@gwl.com
Ka Kau Chan email@example.com
Jason Harrell firstname.lastname@example.org
Rodney Marable email@example.com
Jason K Schechner FiXXiT@off-road.com
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:52 CDT