Arjen de Korte
2010-Nov-29 15:24 UTC
[Nut-upsdev] [nut-commits] svn commit r2706 - in branches/ssl-nss-port: . clients docs m4 server
Citeren Arnaud Quette <aquette op alioth.debian.org>:> dnl ---------------------------------------------------------------------- > -dnl Check for --with-ssl > +dnl Check for with-ssl, and --with-nss or --with-openssl > +dnl Only one can be enabled at a time, with a preference for Mozilla NSS > +dnl if both are availableHaving looked at the differences between Mozilla NSS and OpenSSL a little, I doubt the above is a good idea. Migration from OpenSSL to Mozilla NSS is in all likelihood not going to be transparent to end-users and will require changes in the configuration. While I agree that allowing people an option to choose for Mozilla NSS is good, it would be a grievous mistake to break existing installations (using OpenSSL) because we like the licensing conditions of Mozilla NSS better. So I propose to prefer OpenSSL over Mozilla NSS when both are present and '--with-ssl' is used. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected)
Arnaud Quette
2010-Nov-30 12:50 UTC
[Nut-upsdev] [nut-commits] svn commit r2706 - in branches/ssl-nss-port: . clients docs m4 server
2010/11/29 Arjen de Korte> Citeren Arnaud Quette > > > dnl >> ---------------------------------------------------------------------- >> -dnl Check for --with-ssl >> +dnl Check for with-ssl, and --with-nss or --with-openssl >> +dnl Only one can be enabled at a time, with a preference for Mozilla NSS >> +dnl if both are available >> > > Having looked at the differences between Mozilla NSS and OpenSSL a little, > I doubt the above is a good idea. Migration from OpenSSL to Mozilla NSS is > in all likelihood not going to be transparent to end-users and will require > changes in the configuration. While I agree that allowing people an option > to choose for Mozilla NSS is good, it would be a grievous mistake to break > existing installations (using OpenSSL) because we like the licensing > conditions of Mozilla NSS better. So I propose to prefer OpenSSL over > Mozilla NSS when both are present and '--with-ssl' is used. >it's true that I've been subverted by this topic. I've changed the default to be OpenSSL, which is in phase with the current behavior. Fixed in r2712... thanks for bringing me back to earth ;-) cheers, Arnaud -- Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://www.debian.org Free Software Developer - http://arnaud.quette.free.fr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20101130/087415e0/attachment.htm>
Reasonably Related Threads
- [nut-commits] svn commit r2708 - in branches/ssl-nss-port: clients m4 server
- [nut-commits] svn commit r2610 - branches/silent_build
- Help with /usr/share/sendmail-cf/m4/proto.m4 - fax macro
- SSL flags (was Re: [nut-commits] svn commit r593 - branches/deb_fixes_for_trunk)
- [nut-commits] svn commit r2809 - branches/ssl-nss-port/server