END OF TERMS AND CONDITIONS
How
to
Apply
These
Terms
to
Your
New
libraries
[f you develop a new library, and you want
it
to be
of
the greatest
possible use to the public, we recommend making it free software
that everyone can redistribute and change. You can do so by
permitting redistribution under these terms (or, alternatively, under
the 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 tile to most
effectively convey the exclusion
of
warranty; and each tile should
have at
lea~t
the "copyright" line and a pointer to where the full
notice is found.
<one line to give the library's name and an idea
of
what it does.>
Copyright
(C)
<year> <name
of
authOr>
This library
is
free software; you can redistribute
it
and/or modify it
under the terms
of
the GNU Lesser General Public License as
published
by
the Free Software Foundation; either version
2.1
of
the
License,
or
(at
your option) any later version.
This library
is
distributed in the hope that
it
will be useful, but
W[THOUT ANY WARRANTY; without even the implied warranty
of
MERCHANTAB[L1TY
or
FITNESS FOR A PART[CULAR
PURPOSE. See the GNU Lesser General Public License for more
details.
You should have received a copy
of
the
GNU
Lesser General Public
License along with this library;
if
not, write to the Free Software
Foundation, [nc., 59 Temple Place, Suite 330, Boston, MA 02[ 11-
1307 USA
Also add information on how to contact you by electronic and paper
mail.
You should also get your employer (ifyou work as a programmer)
or
your school, ifany, to sign a "copyright disclaimer" for the library,
if necessary. Here
is
a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest
in
the library
'Frob'
(a library for tweaking knobs) written by James Random
Hacker.
signature
of
Ty Coon, [ April 1990
Ty Coon, President
of
Vice
That's
all there
is
to
it!
Required statements for OpenSSL project
used
in
this product
This product contains OpenSSL (including the library Original
SSLeay), which Sony uses under license with the copyright holder.
In
compliance with a request
by
the copyright holder
of
said
software, Sony conveys the follow ing notice and
a~ks
that you read
it.
Package name: sony-target-gre[-openssl-O.9.8g-Q2020[ .src.rpm
OpenSSL
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:
I.
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.
(httpJlwww.openssl.orgI)"
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 (hnpJlwww.openssl.orgl)"
TH[S SOFTWARE
IS
PROVIDED BY THE OpenSSL PROJECT
"AS
IS" AND ANY EXPRESSED OR [MPLIED WARRANTIES,
INCLUDING, BUT NOT L1M[TED TO,
THE
IMPLIED
WARRANTIES
OF
MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DlSCLA[MED. IN NO EVENT
SHALL THE OpenSSL PROJECT
OR
[TS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, [NCIDENTAL.
SPECIAL, EXEMPLARY, OR CONSEQUENT[AL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMEI\iT
OF
SUBSTITUTE GOODS OR SERVICES; LOSS
OF
USE, DATA,
OR
PROFITS; OR BUS[NESS [NTERRUPT[ON)
HOWEVER CAUSED AND
ON
ANY THEORY
OF
LIABILITY,
WHETHER
[N
CONTRACT, STR[CT L1AB[L1TY,
OR
TORT
(INCLUDING NEGLIGENCE OR OTHERWISE)
ARIS[NG [N ANY WAY
OUT
OF
THE USE OF TH[S
SOFTWARE, EVEN [F ADVISED
OF
THE
POSSIB[L1TY
OF
SUCH DAMAGE.
This product includes cryptographic software written
by
Eric Young
(eay@cryptsoft.com), This product includes software writt,en by
Tim
Hudson (tjh@cryptsoft.com).
Original SSLeay License
Original
SSLeay
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
All rights reserved.
This package
is
an SSL implementation written
by
Eric Young
(eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes
SSL.
This library is free for commercial and non-commercial use as long
as the following conditions are aheared to. The following conditions
apply to all code found
in
this distribution, be
itthe
RC4, RSA, Ihash,
DES, etc., code; not just the SSL code.
The
SSL documentation
included with this distribution
is
covered by the same copylight
terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices
in
the code are not to be removed,
[fthis
package
is
used
in
a product, Eric Young should
be
given
attribution as the author
of
the pallS
of
the library used.
This can be in the form
of
a textual message at program startup
or
in
documentation (online
or
textual) provided with the package.
Redistribution and use
in
source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
l. Redistributions
of
source code must retain the 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 acknowledgement:
"This product includes cryptographic software written
by
Eric
Young (eay@cryptsoft.com)"
The word 'cryptographic' can be left out if the rouines from the
library being used are not cryptographic related :-),
4.
If
you include any Windows specific code (or a derivative
thereof) from the apps directory (application code) you must
include an acknowledgement:
"This product includes software written by Tim Hudson
(tjh@cryptsoft.comj"
-
>
Q.
Q.
::+
o·
::::s
m
-
-
::::s
0'
...
3
m
-
o·
::::s
117
US