forked from syslog-ng/syslog-ng
-
Notifications
You must be signed in to change notification settings - Fork 0
/
COPYING
99 lines (82 loc) · 4.08 KB
/
COPYING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
Copyright (c) 2002-2015 Balabit
Copyright (c) 1996-2015 Balázs Scheidler
syslog-ng is licensed under the combination of the GPL and LGPL licenses.
The syslog-ng core contained in the following subdirectories
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
(please refer to the file LGPL.txt for more details):
lib/
libtest/
syslog-ng/
syslog-ng-ctl/
persist-tool/
tests/loggen/
The syslog-ng modules (modules/ and scl/ subdirectories, except the ones that
declare LGPL-2.1-or-later in their license notices) is free software; you can
redistribute it and/or modify it under the terms of the GNU General Public
License version 2 as published by the Free Software Foundation,
or (at your option) any later version
(please refer to the file GPL.txt for more details).
For file-level license details, check tests/copyright/policy.
FAQ:
====
The questions and answers below try to summarize the intentions behind this
licensing scheme.
Q: Is it possible to create derived works of syslog-ng under the GPL/LGPL
licenses?
A: Yes, that's exactly the point of open source. Works derived from the
plugins will have to use the GPL license, but you can choose to use LGPL for
them as well.
Q: Do I need to sign a Contributory License Agreement in order for my
contribution to be accepted?
A: No, starting with syslog-ng 3.2, you don't need to sign a CLA in order to
have your contributions accepted.
Q: Is it possible to create non-free plugins for syslog-ng?
A: Yes. It is our understanding that plugins are derived works of the
syslog-ng core but not derived works of other plugins. Thus, non-free
plugins are possible, provided they do not link to any of the GPLd plugins
explicitly and the only connection between two plugins is via the syslog-ng
core.
Q: Who is permitted to create non-free plugins for syslog-ng? Is it just
BalaBit (the current copyright holder as of the initial 3.2 release)?
A: No, everyone including BalaBit.
PORTIONS WERE CONTRIBUTED UNDER THE FOLLOWING LICENSES:
======================================================
lib/compat:
/*-
* Copyright (c) 1990, 1993
* The Regents of the University of California. All rights reserved.
*
* This code is derived from software contributed to Berkeley by
* Chris Torek.
*
* 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 acknowledgement:
* This product includes software developed by the University of
* California, Berkeley and its contributors.
* 4. Neither the name of the University nor the names of its contributors
* may be used to endorse or promote products derived from this software
* without specific prior written permission.
*
* THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
* ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
* SUCH DAMAGE.
*/