[226] in sw-release-announce

home help back first fref pref prev next nref lref last post

IS now supports SecureCRT as a secure terminal client for

daemon@ATHENA.MIT.EDU (Jonathan McIndoe Hunt)
Tue Oct 15 12:10:20 2002

Message-Id: <5.2.0.5.0.20021015114450.03ca0c10@po12.mit.edu>
Date: Tue, 15 Oct 2002 12:08:00 -0400
To: itpartners@MIT.EDU, winpartners@MIT.EDU, sw-release-announce@MIT.EDU
From: Jonathan McIndoe Hunt <jmhunt@MIT.EDU>
Cc: infosys@MIT.EDU, itag@MIT.EDU, security-internal@MIT.EDU
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Date: Tuesday, 15 October 2002
To: MIT Community: itpartners@mit.edu, winpartners@mit.edu, 
sw-release-announce@mit.edu
From: Jonathan McIndoe Hunt <jmhunt@mit.edu>
Cc: infosys@mit.edu, security-internal@mit.edu, itag@mit.edu


Good Afternoon,

Information Systems is pleased to announce support for SecureCRT 3.4.6 as a 
secure terminal client.  SecureCRT is an SSH terminal client that can be 
used like Host Explorer to connect the Athena Dialup machines.  SecureCRT 
does not work with TN3270, so it cannot be used to connect to MITVMA or MITVMC.

Who should install/upgrade and why?
--------------------------------------------------------------
If you have been receiving an insecure telnet connections warning and have 
not resolved it by using SecureCRT or Host Explorer, then you should 
install SecureCRT 3.4.6.

If you have a working secure terminal client such as a previous version of 
SecureCRT or Host Explorer, you do not need to install or upgrade.

The Software Release Team plans in the next two months to create a 
customized installer for SecureCRT 4.0.  The customized installer will 
include some pre-configured standard connections, such as 
athena.dialup.mit.edu, and will not require the license key information to 
be entered manually.  If you do not need SecureCRT today, then we recommend 
waiting until the customized installer is available.


Notable Feature
-----------------------------
- SSH2 support


Known Issues
------------------------------
- SecureCRT can be configured to be insecure.  If you use the Telnet 
protocol, all information you send will be in the clear.  Be sure to use 
the protocol SSH2.

- License Key data needs to be entered by an Administrator.


Where to get SecureCRT
-----------------------------------------
SecureCRT and the license key can be downloaded from the MIT Software 
Distribution page at: http://web.mit.edu/software/

Please review the documentation for the appropriate settings for SecureCRT at:
http://web.mit.edu/is/help/securecrt

If you have questions or need assistance, please contact the Computing Help 
Desk at:
  - email: computing-help@mit.edu
  - phone: x3-1102
  - web: http://web.mit.edu/helpdesk/

Information Systems thanks the MIT Media Lab for making SecureCRT available 
to the MIT Community.

Thanks,
Jon
___________________________________________
Jonathan M. Hunt
Windows Platform Coordinator and Team Leader
Software Release Team
Information Systems
W92-191 x3-0172

DISCLAIMER:
------------
The Software Release Team does not distribute software releases, updates or 
patches through e-mail. Please DISREGARD ANY MESSAGES WITH ATTACHMENTS SENT 
BY THIS TEAM. Most likely, they are forged and will contain viruses and/or 
unsolicited and potentially offensive content.  


home help back first fref pref prev next nref lref last post