<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.4712.0">
<TITLE>RE: Secure Server Management Report</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>I have been using secure crt from:</FONT>
</P>
<P><FONT SIZE=2><A HREF="http://www.core-sdi.com">http://www.core-sdi.com</A></FONT>
</P>
<P><FONT SIZE=2>This SSH client works well with:</FONT>
<BR><FONT SIZE=2>JFW Versions: 3.70, 3.71, & 4.00. </FONT>
</P>
<P><FONT SIZE=2>Secure CRT is share ware, and I don't remember the licence cost. The only short coming that I have found with Secure CRT is that it does not have an implementation of SCP, which would eliminate the need for secure ftp.</FONT></P>
<BR>
<P><FONT SIZE=2>Stephen Dawes B.A. B.Sc.</FONT>
<BR><FONT SIZE=2>Web Business Office, The City of Calgary</FONT>
<BR><FONT SIZE=2>PHONE: (403) 268-5527. </FONT>
<BR><FONT SIZE=2>FAX: (403) 268-6423</FONT>
<BR><FONT SIZE=2>E-MAIL ADDRESS: Stephen.Dawes@gov.calgary.ab.ca </FONT>
<BR><FONT SIZE=2>Internet: <A HREF="http://www.gov.calgary.ab.ca">http://www.gov.calgary.ab.ca</A></FONT>
</P>
<BR>
<P><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Janina Sajka [<A HREF="mailto:janina@afb.net">mailto:janina@afb.net</A>]</FONT>
<BR><FONT SIZE=2>> Sent: 2001 October 01 12:41 PM</FONT>
<BR><FONT SIZE=2>> To: Charles Crawford; Matt Campbell; Earlene Hughes</FONT>
<BR><FONT SIZE=2>> Cc: speakup@braille.uwo.ca</FONT>
<BR><FONT SIZE=2>> Subject: Secure Server Management Report</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Dear Colleagues:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> This report summarizes my explorations of functionality and </FONT>
<BR><FONT SIZE=2>> accessibility</FONT>
<BR><FONT SIZE=2>> in current SSH clients for Windows. As you will recall, I (and others)</FONT>
<BR><FONT SIZE=2>> have strongly advised against using telnet and ftp for </FONT>
<BR><FONT SIZE=2>> administration of</FONT>
<BR><FONT SIZE=2>> ACB's remote web server simply because these applications are </FONT>
<BR><FONT SIZE=2>> insecure.</FONT>
<BR><FONT SIZE=2>> Rather, SSH is recommended because it provides the same </FONT>
<BR><FONT SIZE=2>> functionality but</FONT>
<BR><FONT SIZE=2>> in a manner where all of the information transmitted across the public</FONT>
<BR><FONT SIZE=2>> Internet has been secured with strong data encryption. This is</FONT>
<BR><FONT SIZE=2>> particularly important for usernames and passwords which </FONT>
<BR><FONT SIZE=2>> allow access to</FONT>
<BR><FONT SIZE=2>> system level functions on this remote server. And, such security</FONT>
<BR><FONT SIZE=2>> precautions have only become more important since the events </FONT>
<BR><FONT SIZE=2>> of September</FONT>
<BR><FONT SIZE=2>> 11 last.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Fortunately, the news for ACB is very good. I will point you </FONT>
<BR><FONT SIZE=2>> to a fully</FONT>
<BR><FONT SIZE=2>> accessible and fully featured ftp client with full support </FONT>
<BR><FONT SIZE=2>> for ssh2--the</FONT>
<BR><FONT SIZE=2>> current standard. This should take care of the need to move </FONT>
<BR><FONT SIZE=2>> files back and</FONT>
<BR><FONT SIZE=2>> forth very nicely. The news for command line access isn't </FONT>
<BR><FONT SIZE=2>> quite as good,</FONT>
<BR><FONT SIZE=2>> though it is still not bad. Herewith the details:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> 1.) File Transfer Agents</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> There is really only one choice here. CuteFTP Pro 1.0 has </FONT>
<BR><FONT SIZE=2>> absolutely everything ACB needs to manage files on its remote</FONT>
<BR><FONT SIZE=2>> server securely. CuteFTP Pro stands head and shoulders above </FONT>
<BR><FONT SIZE=2>> the competition both on accessibility and on ftp features.</FONT>
<BR><FONT SIZE=2>> It is, unfortunately, not a free software program, but it is </FONT>
<BR><FONT SIZE=2>> very excellent all the way around. Be sure you get CuteFTP</FONT>
<BR><FONT SIZE=2>> Pro 1.0, and not the older CuteFtp 3.5 or 4.0 clients which </FONT>
<BR><FONT SIZE=2>> do NOT support ssh. A free 30 day trial copy can be</FONT>
<BR><FONT SIZE=2>> downloaded from GlobalScape, the manufacturer of CuteFTP Pro at:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> <A HREF="http://www.globalscape.com/download/index.shtml">http://www.globalscape.com/download/index.shtml</A></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> My second, and very viable, choice for managing these files </FONT>
<BR><FONT SIZE=2>> remotely is the DOS command line utilities that are</FONT>
<BR><FONT SIZE=2>> available in the SSH for Windows 32-bit operating </FONT>
<BR><FONT SIZE=2>> environments client available free of charge to nonprofits at</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> <A HREF="http://www.ssh.com">http://www.ssh.com</A></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Regretably, the Windows utilities in this package are only </FONT>
<BR><FONT SIZE=2>> partially accessible. But, they are also only partly as</FONT>
<BR><FONT SIZE=2>> capable as Cute FTP -- lacking such important features as </FONT>
<BR><FONT SIZE=2>> "resume upload." Still, the DOS ports of the unix commands scp</FONT>
<BR><FONT SIZE=2>> and sftp will work very well for anyone who still has good </FONT>
<BR><FONT SIZE=2>> speech access to DOS;</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> 2.) Terminal Access</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> The options for a good command line on the web server are not </FONT>
<BR><FONT SIZE=2>> as clear as for file management. Fortunately, though,</FONT>
<BR><FONT SIZE=2>> there are very good secure substitutes for telnet, and their </FONT>
<BR><FONT SIZE=2>> accessibility is probably no less than the accessibility</FONT>
<BR><FONT SIZE=2>> for the various telnet clients. Let me explain:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Not unlike the circumstances in available telnet clients, </FONT>
<BR><FONT SIZE=2>> available ssh clients range from fully accessible clients to</FONT>
<BR><FONT SIZE=2>> not so accessible ones. And, the reasons for this are </FONT>
<BR><FONT SIZE=2>> substantially the same because, after the connection is made, what</FONT>
<BR><FONT SIZE=2>> telnet presents onscreen is no different than what ssh </FONT>
<BR><FONT SIZE=2>> presents onscreen.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> So, if you think that telnet is accessible on Windows, you </FONT>
<BR><FONT SIZE=2>> will likely get the same level of accessibility from the</FONT>
<BR><FONT SIZE=2>> SSH Client for Windows available from:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> <A HREF="http://www.ssh.com">http://www.ssh.com</A></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> In order to get the same functionality, however, you will </FONT>
<BR><FONT SIZE=2>> likely need to apply whatever set files are associated with</FONT>
<BR><FONT SIZE=2>> your Windows telnet client to this SSH application.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> If, on the other hand, you are able to run in DOS, you will </FONT>
<BR><FONT SIZE=2>> find the command line version which comes with this</FONT>
<BR><FONT SIZE=2>> application vastly superior. This DOS client simply works </FONT>
<BR><FONT SIZE=2>> with asap or vocal-eyes.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> CONCLUSIONS</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> The Windows CuteFTP Pro 1.0 client should be used for secure </FONT>
<BR><FONT SIZE=2>> remote file management;</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> The DOS SSH2.EXE client from ssh.com should be used for </FONT>
<BR><FONT SIZE=2>> secure remote terminal access;</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> The telnet server should be removed from the web server;</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> FTP access should be limited to anonymous access only;</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> ADDITIONAL NOTES</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> There is yet another SSH application available on Windows </FONT>
<BR><FONT SIZE=2>> called PuTTY. While it is not as accessible, in my view, as</FONT>
<BR><FONT SIZE=2>> the applications named above, it could be as accessible if a </FONT>
<BR><FONT SIZE=2>> competent programmer were to fix the interface. This is</FONT>
<BR><FONT SIZE=2>> possible because PuTTY is an open source application. The </FONT>
<BR><FONT SIZE=2>> source code, documentation, and current executables for PuTTY</FONT>
<BR><FONT SIZE=2>> can be found at:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> <A HREF="http://www.chiark.greenend.org.uk/~sgtatham/putty/">http://www.chiark.greenend.org.uk/~sgtatham/putty/</A></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Respectfully Submitted,</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> -- </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Janina Sajka, Director</FONT>
<BR><FONT SIZE=2>> Technology Research and Development</FONT>
<BR><FONT SIZE=2>> Governmental Relations Group</FONT>
<BR><FONT SIZE=2>> American Foundation for the Blind (AFB)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Email: janina@afb.net Phone: (202) 408-8175</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Chair, Accessibility SIG</FONT>
<BR><FONT SIZE=2>> Open Electronic Book Forum (OEBF)</FONT>
<BR><FONT SIZE=2>> <A HREF="http://www.openebook.org">http://www.openebook.org</A></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Will electronic books surpass print books? Read our white paper,</FONT>
<BR><FONT SIZE=2>> Surpassing Gutenberg, at <A HREF="http://www.afb.org/ebook.asp">http://www.afb.org/ebook.asp</A></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Download a free sample Digital Talking Book edition of Martin Luther</FONT>
<BR><FONT SIZE=2>> King Jr's inspiring "I Have A Dream" speech at</FONT>
<BR><FONT SIZE=2>> <A HREF="http://www.afb.org/mlkweb.asp">http://www.afb.org/mlkweb.asp</A></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Learn how to make accessible software at</FONT>
<BR><FONT SIZE=2>> <A HREF="http://www.afb.org/accessapp.asp">http://www.afb.org/accessapp.asp</A></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> _______________________________________________</FONT>
<BR><FONT SIZE=2>> Speakup mailing list</FONT>
<BR><FONT SIZE=2>> Speakup@braille.uwo.ca</FONT>
<BR><FONT SIZE=2>> <A HREF="http://speech.braille.uwo.ca/mailman/listinfo/speakup">http://speech.braille.uwo.ca/mailman/listinfo/speakup</A></FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
</BODY>
</HTML>