92
Since version 0.4.2, the GnuTLS library has been released under the GNU
93
Lesser General Public License (LGPL). Previous versions were licensed
94
under the GNU General Public License (GPL).
96
We changed the license for most of the GnuTLS components because other
97
free libraries exist and offer similar functionality with lax licenses.
98
We want GnuTLS to be usable in the same places as those other libraries.
99
We kept some parts of GnuTLS under the GPL because they are unique, and
100
the terms of the license under GPL provides free software projects (which
101
deserve our help) an advantage over non-free projects (which do not
102
deserve our help, since they refuse to share with us). For information, see
103
http://www.gnu.org/philosophy/why-not-lgpl.html.
92
Since GnuTLS version 3.0.0, the core library has been released under
93
the GNU Lesser General Public License (LGPL) version 3 or later.
105
95
The GNU LGPL applies to the main GnuTLS library, while the
106
gnutls-extra and gnutls-openssl libraries are under the GPL. The
107
gnutls library is located in the lib/ directory, while the
108
gnutls-extra and gnutls-openssl library is at libextra/.
110
For the GnuTLS version 3.0.0 release we upgraded the license of the
111
core library to LGPL version 3 or later.
96
included applications as well as gnutls-extra and gnutls-openssl
97
libraries are under the GNU GPL version 3. The gnutls library is
98
located in the lib/ directory, while the applications in src/ and
99
gnutls-extra and gnutls-openssl library are at libextra/.
113
101
For any copyright year range specified as YYYY-ZZZZ in this package
114
102
note that the range specifies every single year in that closed interval.
119
Currently GnuTLS needs testing. Thorough testing is very important and
120
expensive. Often times, the developers do not have access to a particular
121
piece of hardware or configuration to reproduce a scenario. Notifying
122
the developers about a possible bug will greatly help the project.
107
Thorough testing is very important and expensive. Often, the
108
developers do not have access to a particular piece of hardware or
109
configuration to reproduce a scenario. Notifying the developers about a
110
possible bug will greatly help the project.
124
112
If you believe you have found a bug, please report it to bug-gnutls@gnu.org
125
113
together with any applicable information. A web interface for the system
128
116
Applicable information would include why the issue is a GnuTLS bug (if
129
117
not readily apparent), output from 'uname -a', the version of the library or
130
tool being used, a stack trace if available ('bt full' if under gdb), and
131
perhaps a network trace. Vague queries or piecemeal messages are difficult
132
to act upon and don't help the development effort.
118
tool being used, a stack trace if available ('bt full' if under gdb or
119
valgrind output), and perhaps a network trace. Vague queries or piecemeal
120
messages are difficult to act upon and don't help the development effort.
134
Additional information can be found at the project's Bug Report page at
135
http://www.gnu.org/software/gnutls/manual/html_node/Bug-Reports.html.
122
Additional information can be found at the project's manual at:
123
http://www.gnu.org/software/gnutls/documentation.html.
140
Patches are welcome and encouraged. Details of contributing can be found
141
at http://www.gnu.org/software/gnutls/manual/html_node/Contributing.html.
143
Patches are submitted through the bug tracking system or to the
144
mailing list. When submitting patches, please be sure to use sources
145
from the git repository, and preferrably from the master branch. To
146
create a patch for the project from a local git repository, please use
147
the following commands. 'gnutls' should be the local directory of a
128
Patches are welcome and encouraged. Patches can be submitted through the
129
bug tracking system or the mailing list. When submitting patches, please
130
be sure to use sources from the git repository, and preferrably from the
131
master branch. To create a patch for the project from a local git repository,
132
please use the following commands. 'gnutls' should be the local directory
133
of a previous git clone.
151
136
git add the-file-you-modified.c another-file.c
added
removed
README
