279TOSHIBA 23/26LC100 [NewCID]その他USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSSOF DATA OR DATA BEING RENDERED INACCURATE ORLOSSES SUSTAINED BY YOU OR THIRD PARTIES OR AFAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHERSOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HASBEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.END OF TERMS AND CONDITIONSHow to Apply These Terms to Your New LibrariesIf you develop a new library, and you want it to be of the greatestpossible use to the public, we recommend making it free softwarethat everyone can redistribute and change. You can do so bypermitting redistribution under these terms (or, alternatively, underthe terms of the ordinary General Public License).To apply these terms, attach the following notices to the library.It is safest to attach them to the start of each source file to mosteffectively convey the exclusion of warranty; and each file shouldhave at least the "copyright" line and a pointer to where the fullnotice is found.<one line to give the library's name and a brief idea of what itdoes.>Copyright (C) <year> <name of author>This library is free software; you can redistribute it and/ormodify it under the terms of the GNU Lesser General PublicLicense as published by the Free Software Foundation;either version 2 of the License, or (at your option) any laterversion.This library is distributed in the hope that it will be useful, butWITHOUT ANY WARRANTY; without even the impliedwarranty of MERCHANTABILITY or FITNESS FOR APARTICULAR PURPOSE. See the GNU Lesser GeneralPublic License for more details.You should have received a copy of the GNU LesserGeneral Public License along with this library; if not, write tothe Free Software Foundation,Inc., 59 Temple Place, Suite330, Boston, MA 02111-1307 USAAlso add information on how to contact you by electronic andpaper mail.You should also get your employer (if you work as a programmer)or your school, if any, to sign a "copyright disclaimer" for thelibrary, if necessary. Here is a sample; alter the names: Yoyodyne,Inc., hereby disclaims all copyright interest in the library `Frob' (alibrary for tweaking knobs) written by James Random Hacker.<signature of Ty Coon>,1 April 1990Ty Coon,President of ViceThat's all there is to it!E x h i b i t CThis is a version (aka dlmalloc) of malloc/free/realloc written byDoug Lea and released to the public domain. Use, modify, andredistribute this code without permission or acknowledgement inany way you wish. Send questions, comments, complaints,performance data, etc to dl@cs.oswego.eduVERSION 2.7.2 Sat Aug 17 09:07:30 2002 Doug Lea (dl at gee)Note: There may be an updated version of this malloc obtainable at ftp://gee.cs.oswego.edu/pub/misc/malloc.cCheck before installing!E x h i b i t DLICENSE ISSUESThe OpenSSL toolkit stays under a dual license, i.e. both theconditions of the OpenSSL License and the original SSLeaylicense apply to the toolkit.See below for the actual license texts. Actually both licenses areBSD-style Open Source licenses. In case of any license issuesrelated to OpenSSL please contact openssl-core@openssl.org.OpenSSL LicenseCopyright (C) 1998-2002 The OpenSSL Project. All rightsreserved.Redistribution and use in source and binary forms, with orwithout modification, are permitted provided that thefollowing conditions are met:1. Redistributions of source code must retain the abovecopyright notice, this list of conditions and the followingdisclaimer.2. Redistributions in binary form must reproduce theabove copyright notice, this list of conditions and thefollowing disclaimer in the documentation and/or othermaterials provided with the distribution.3. All advertising materials mentioning features or use ofthis software must display the following acknowledgment:"This product includes software developed by theOpenSSL 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 derivedfrom this software without prior written permission. Forwritten permission, please contact openssl-core@openssl.org.5. Products derived from this software may not be called"OpenSSL" nor may "OpenSSL" appear in their nameswithout prior written permission of the OpenSSL Project.6. Redistributions of any form whatsoever must retain thefollowing acknowledgment:"This product includes software developed by theOpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"THIS SOFTWARE IS PROVIDED BY THE OpenSSLPROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF MERCHANTABILITYAND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE OpenSSLPROJECT OR ITS CONTRIBUTORS BE LIABLE FORANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENTOF SUBSTITUTE GOODS OR SERVICES; LOSS OFUSE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION)HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OROTHERWISE) ARISING IN ANY WAY OUT OF THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.This product includes cryptographic software written byEric Young (eay@cryptsoft.com). This product includessoftware written by Tim Hudson (tjh@cryptsoft.com).Original SSLeay LicenseCopyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)All rights reserved.This package is an SSL implementation written by EricYoung (eay@cryptsoft.com).The implementation was written so as to conform withNetscapes SSL.This library is free for commercial and non-commercialuse as long as the following conditions are aheared to.The following conditions apply to all code found in thisdistribution, be it the RC4, RSA, lhash, DES, etc., code;not just the SSL code. The SSL documentation includedwith this distribution is covered by the same copyrightterms except that the holder is Tim Hudson(tjh@cryptsoft.com).Copyright remains Eric Young's, and as such anyCopyright notices in the code are not to be removed.If this package is used in a product, Eric Young should begiven attribution as the author of the parts of the libraryused.This can be in the form of a textual message at programstartup or in documentation (online or textual) providedwith the package.#8(p273-281)_2326LC100 05.1.21, 10:41 PM Page 279 Adobe PageMaker 6.5J/PPCブラック