James Jones
2006-Sep-13 15:27 UTC
[asterisk-users] Copyright issues with libcurl and OpenSSL
Does anyone know why the g729 codec module sold by diguim does not display the OpenSSL copyright information. Do they have an agreement with OpenSSL to not display the Copyright Information that is required ny their license when distributed as part of a binary that uses OpenSSL. The registration program uses libcurl and openssl (both statically linked) to register the g.729 codec (and they said soon other products). This too does not display the required information about other peoples open source code. If they don't have already signed agreements with the developer of libCurl and OpenSSL they are distrabuting libCURL and OpenSSL with giving the correct copyright information with register program and then they are making money off the OpenSSL libs with they sell the g729 codec with out giving correct copyright information. I just want to confirm they have agreement not to show copyright information for the products, if not it could cause legal issues for people who work with Asterisk when they distribute it to their clients/customers. I have enclosed relivent snippites of the licenses in question and links to the full licenses. libCurl: http://curl.haxx.se/docs/copyright.html COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1996 - 2006, Daniel Stenberg, <daniel@haxx.se>. All rights reserved. Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder. OpenSSL: http://www.openssl.org/source/license.html /* =================================================================== * Copyright (c) 1998-2006 The OpenSSL Project. All rights reserved. * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * * 2. Redistributions in binary form must reproduce the above copyright * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. All advertising materials mentioning features or use of this * software must display the following acknowledgment: * "This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit. (http://www.openssl.org/)" * * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to * endorse or promote products derived from this software without * prior written permission. For written permission, please contact * openssl-core@openssl.org. * * 5. Products derived from this software may not be called "OpenSSL" * nor may "OpenSSL" appear in their names without prior written * permission of the OpenSSL Project. * * 6. Redistributions of any form whatsoever must retain the following * acknowledgment: * "This product includes software developed by the OpenSSL Project * for use in the OpenSSL Toolkit (http://www.openssl.org/)"
Matt Riddell (IT)
2006-Sep-13 15:35 UTC
[asterisk-users] Copyright issues with libcurl and OpenSSL
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 James Jones wrote:> Does anyone know why the g729 codec module sold by diguim does not > display the OpenSSL copyright information. Do they have an agreement > with OpenSSL to not display the Copyright Information that is required > ny their license when distributed as part of a binary that uses OpenSSL. > > The registration program uses libcurl and openssl (both statically > linked) to register the g.729 codec (and they said soon other > products). This too does not display the required information about > other peoples open source code.Don't know about libcurl, but have you read the LICENCE file in the Asterisk directory? "Specific permission is also granted to link Asterisk with OpenSSL and OpenH323." I assume if they have specific permission, then they've sorted something with the OpenSSL people. Best place to ask this though is: http://licensing.digium.com/main_page.php - -- Cheers, Matt Riddell _______________________________________________ http://www.sineapps.com/news.php (Daily Asterisk News - html) http://wap.sineapps.com (Daily Asterisk News for your cellphone) http://feeds.feedburner.com/AsteriskNews (Daily Asterisk News - rss) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFCIe/S6d5vy0jeVcRAiT0AJ9LNMoQsqK+CkVoLbktqy/sQu+hAACffXnV 9AwB6HnOof0IO3FEtOPyhq4=hjhw -----END PGP SIGNATURE-----