Hi Ian, Greg, et al.,

SSH Secure Shell version 3.0 handles licenses 
differently than previous versions did.

Uninstall all instances of SSH Secure Shell 
using Add/Remove programs.  Then go to 
ftp://ftp.ssh.com/pub/ssh and download the 
SSH Windows client 3.0 binary found there.  

SSH Secure Shell Windows client 3.0 (Build 199) 
and later works the following way:

- If the installation package does not contain a
license.dat file at all, the software will run 
in non-commercial mode.

For users, the most visible change is that 
the non-commercial version of SSH Secure Shell Windows 
Client does not require a license.dat file any more.
Previously all non-commercial users had to apply for 
a license from our ecommerce site.

If you downloaded a version prior to Build 199, 
please discard that binary and download Build 199 
instead.  If you have a license.dat file in the install
path for SSH Secure Shell, please rename or move that
file elsewhere so that the software will not attempt 
to use it.

Hope this helps.

Best Regards,

Steph

Ian Carter White wrote:
> 
> Yes! I had the same problem yesterday.
> 
> Ian Carter White
> Essex Symphony Orchestra
> [EMAIL PROTECTED]
> 
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Greg
> MacKinnon
> Sent: Friday, July 13, 2001 12:27 PM
> To: [EMAIL PROTECTED]
> Subject: SSH 3.0 license files
> 
> We are having difficulty using our new SSH 3.0 binary for Windows
> workstations...
> 
> On startup, we receive a "license file does not contain the required
> data" error.  The included license.dat file contains a reference to SSH
> 2.4, not 3.0.  None of the license.dat files I have access to on the
> commerce.ssh.com site contain SSH 3.0 license data.
> 
> Have any other non-commercial (university) users had similar problems?
> Any solutions?

-- 
*********************************
Stephanie Thomas
Technical Support Specialist
SSH Secure Shell
GIAC Certified
Unix Security Administrator
SSH Communications Security Inc.
http://www.ssh.com/support/ssh
*********************************

Reply via email to