Page History
Chaos Player
...
Copyright 20222024, Chaos Software EOOD. Portions contributed and copyright held by others as indicated.
...
| Excerpt Include | ||||||
|---|---|---|---|---|---|---|
|
OpenSSL
...
Version 1.1
LICENSE ISSUES
==============
The OpenSSL toolkit stays under a double license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit.
See below for the actual license texts.
OpenSSL License
...
Copyright (c) 1998-2019 The OpenSSL Project. All rights reserved.
...
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License
...
Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
...
The licence and distribution terms for any publically available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution licence [including the GNU Public Licence.]
FFmpeg library under LGPL v2.1
...
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you".
...
How to Apply These Terms to Your New Libraries
...
If 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 file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
...
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,
...
Lesser General Public License for more details.
...
You should have received a copy of the GNU Lesser General Public
...
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
...
Also add information on how to contact you by electronic and paper mail.
...
That's all there is to it!
GNU GENERAL PUBLIC LICENSE
Version 2, June 1991
...
Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
...
How to Apply These Terms to Your New Programs
...
If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software; you can redistribute it and/or modify
...
(at your option) any later version.
...
This program is distributed in the hope that it will be useful,
...
GNU General Public License for more details.
...
You should have received a copy of the GNU General Public License along
...
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
Also add information on how to contact you by electronic and paper mail.
...
under certain conditions; type `show c' for details.
The hypothetical commands show w' and show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than show w' and show c'; they could even be mouse-clicks or menu items--whatever suits your program.
You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.
...