199
199
------------------------------------------------------------------------------
201
Note: SSL support is still considered development code, since various
202
bits of the implementation may change in the near future. One thing
203
that may happen before long is support for gnutls to avoid licensing
201
SSL support should be considered stable but purposely underdocumented
202
since various bits of the implementation or configuration may change in
203
the future. In other words, if you use this and it stops working after
204
an upgrade, come back to this file to find out what changed.
206
206
This is why the other documentation doesn't mention any of these
207
207
directives yet. SSL support is a treat for those of you that RTFM.
209
There are also potential licensing issues for people who ship binary
210
packages since NUT is GPL and OpenSSL is not compatible with it. You
211
can still build and use it yourself, but you can't distribute the
212
results of it. Or maybe you can. It depends on what you consider
213
"essential system software", and some other legal junk that I'm not
216
Other packages have solved this by explicitly stating that an exception
217
has been granted. That is (purposely) impossible here, since NUT is the
218
combined effort of many people, and all of them would have to agree to a
219
license change. This is actually a feature, since it means nobody can
220
unilaterally run off with the source - not even me.
222
It would be nice if we could also link against gnutls to avoid the
209
225
Potential problems
210
226
==================
227
243
If that's after the current date, you need to generate another cert/key
228
244
pair using the procedure above.
249
There are probably other ways to handle this, involving keys which have
250
been signed by a CA you recognize. Contact your local SSL guru.
added
removed
docs/ssl.txt
