Jeffrey Altman writes:
> > In short, SSH grants universities around the world a free right to use
> > SSH Secure Shell free of charge within their organization for
> > non-commercial use. This includes both Windows and Unix versions.
>
> Please be very specific with your definition of "non-commercial use"
> in your license. Other licenses that were supposedly "free for
> non-commercial use" have not been because they include
The intention is to make it very generally available for universities
(i.e., removing the problems that have existed in the old SSH2
license).
The new license agreement should be ready in a few days.
Tatu
>
> . references to special treatment for administrative tasks
>
> once the software is installed it is impossible to restrict
> its use. If restrictions on use are applied, then the software
> (especially on a server) cannot be installed.
>
> . restrictions on distribution as part of revenue generating
> activities.
>
> many Universities have special computing fees separate from
> tuition or labs fees to cover the cost of support, network
> infrastructure to residence halls, and software distribution.
> These fees constitute revenue generation and prohibit the
> distribution of the software unless the fees are abandoned
> (a thoroughly impractical idea.)
>
> Other items of concern to be addressed in the license:
>
> . it is impossible for a University to restrict the use
> of the software once distributed to students, faculty and
> staff to only University activities. Nor is it feasible
> for the University to be responsible for the return or
> destruction of the software once the recipient leaves the
> University community.
>
> . Universities often have special computing infrastructures
> which need to be supported. Do the Universities have the
> right to modify the code to support their needs? Will
> Windows source code be made available?
>
>
>
>
--
SSH Communications Security http://www.ssh.com/
SSH IPSEC Toolkit http://www.ipsec.com/
SSH Secure Shell http://www.ssh.com/ssh
