Re: Gettting Openssh 3.4p1 working on Unixware 7.11

From: Bill Vermillion (bv_at_wjv.comREMOVE)
Date: 10/29/03


Date: Wed, 29 Oct 2003 05:05:02 GMT

In article <rnitpvcbitsb3ilcldfrg5kp51vfof1gk0@4ax.com>,
FyRE <FyRE@toktik.demon.ku.oc.x> wrote:
>On 27 Oct 2003 17:54:21 -0800, davidw@justinc.com (D. Wolf - Just
>Solutions, Inc.) wrote:

>>I have download the skunkware Openssh 3.4p1, prngd-0.9.23, zlib-1.1.4
>>and I cannot get ssh to work....

>Good. Hey, why not use SCO's own ssh daemon? What's that you say? "SCO
>don't supply such software?" Well that's too bad, Dave. The company
>that makes and distributes your chosen OS doesn't recognise the GPL.

Makes absolutely no difference in this case. Go to openssh.org and
you will see that openssh does not use the GPL.

========================================
This file is part of the OpenSSH software.

The licences which components of this software fall under are as
follows. First, we will summarize and say that all components
are under a BSD licence, or a licence more free than that.

OpenSSH contains no GPL code.

1)
     * Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
     * All rights reserved
     *
     * As far as I am concerned, the code I have written for this software
     * can be used freely for any purpose. Any derived versions of this
     * software must be clearly marked as such, and if the derived work is
     * incompatible with the protocol description in the RFC file, it must be
     * called by a name other than "ssh" or "Secure Shell".

========================================

And it continues on - you can got to www.openssh.org and read it
for your self. That code is wide open to do anything you wish,
except remove the copyright statements, and if you change anything
to make it incomaptible you can't call it ssh or Secure Shell

>So in effect they don't recognise the licence. Thus, using GPL'ed
>software in SCO products is a violation of the licence. You're opening
>yourself, and/or your customers to legal action.

But not for SSH.

Try another piece of software for your argument to use as an
example.

Bill

-- 
Bill Vermillion - bv @ wjv . com


Relevant Pages

  • Re: two SSH compatibility scenarios: can it work?
    ... We are required to use SSH to log into the Engineering lab machines. ... > server software displays this header upon telnet connection to port 22. ... I still use Windows on my notebook for application compatibility. ... > running OpenSSH 3.4p1. ...
    (comp.security.ssh)
  • Re: OpenSSH, Telnet, Windows Authentication and double-hops
    ... deployment on a Windows network. ... Does this mean that you are setting SSH port forwarding ... does not provide the other side with either a Kerberos ticket, ... We're focusing on the OpenSSH for Windows distribution. ...
    (comp.security.ssh)
  • Re: ssh compatability issues
    ... >> without keeping two versions of ssh around on my home computer. ... running the OpenSSH server that comes with Solaris ... By 'some old security problems with that' I was not sure if you meant ...
    (comp.security.ssh)
  • Re: Solaris 9 SSH: HostbasedAuthentication?
    ... > Subject: Solaris 9 SSH: HostbasedAuthentication? ... > authentication. ... I'm gathering that the OpenSSH version it's based on didn't have ...
    (Focus-SUN)
  • Re: [openssh-unix-announce] Re: Upcoming OpenSSH vulnerability (fwd)
    ... Is OpenSSH 3.3 now part of the base system? ... older versions of ssh are vulnerable or not. ... I have to say that I side with Theo here: ... we wouldn't need OpenSSH. ...
    (FreeBSD-Security)