Date: Fri, 1 Dec 2006 09:18:42 -0800 From: Chuck Swiger <cswiger@mac.com> To: Dmitry Pryanishnikov <dmitry@atlantis.dp.ua> Cc: FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: sshd. "UseDNS no" ignored? Message-ID: <C8B42905-2A2B-4959-AF07-C3B4E6860930@mac.com> In-Reply-To: <20061201120708.D81433@atlantis.atlantis.dp.ua> References: <d8a4930a0611210211q4920bfdkf7f0400c69df2689@mail.gmail.com> <4563126E.2060904@math.missouri.edu> <20061129143330.T82233@atlantis.atlantis.dp.ua> <Pine.LNX.4.58.0611301903110.14631@mussel.ucc.gu.uwa.edu.au> <20061130205045.A96066@atlantis.atlantis.dp.ua> <3BC50132-2DD9-4FAA-8320-C945DF4BFD48@mac.com> <20061201120708.D81433@atlantis.atlantis.dp.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 1, 2006, at 2:14 AM, Dmitry Pryanishnikov wrote: > Hello! Hi... > On Thu, 30 Nov 2006, Chuck Swiger wrote: >>> http://www.ssh.com/support/downloads/secureshellserver/non- >>> commercial.html >>> contains both download URLs and "Non-commercial license agreement >>> for SSH Secure Shell for Servers" link. >> >> Right, and the license restriction to non-commercial use only >> means that SSH Secure Shell is not OSI Open Source, because it >> violates OSD #6: > > And I didn't say that it's the OSI Open Source. I wrote "(which > is also open-source)", not even "Open Source". So I didn't mean > that you can just copy&paste their sources into OpenSSH. [ ... ] I quoted what you said in my prior message; you need not remind me of your specific words. Claiming to have an "open source" licensed codebase isn't of much value if that codebase cannot be used freely. For example, if someone wrote some software, and put it under the BSD license, yet only released binaries without ever releasing the source code, claiming that the software is under an "open source" license may be technically true, but in practice is disingenuous and not especially useful. I'd really prefer that people not claim a license is "open source" without submitting their license for consideration to the OSI board via the <license-discuss@opensource.org> mailing list, and having it be approved. While one may choose not to follow the process, doing so means that you are choosing not to work with people who are pretty good at evaluating licenses and making sure that those licenses are well-drafted, legally consistent, and support the goals of the open source community. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C8B42905-2A2B-4959-AF07-C3B4E6860930>