Since there are no bug-reports on launchpad the most valid argument is probably that the changes have been implemented in Debian-Stretch (9.1) and also backported to stretch-backports.
See discussion (and included links) here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867567 [Impact] * Currently nagios-nrpe-server on zesty cannot talk to existing infrastructure using older nagios/icinga server without disabling SSL (or plainly pinning nagios-nrpe-server to xenial) [Test Case] * Setup nagios/icinga server using distribution based on wheezy/jessy (eg. ubuntu trusty/xenial) * Setup nagios node using zesty * Setup nagios-node to allow connections from nagios/icinga server * Invoking nrpe-plugin fails with "Could not complete SSL handshake" (See https://github.com/NagiosEnterprises/nrpe/issues/113 for details about this) [Regression Potential] * Seeing this implemented in Debian 9.1 and stretch-backport proably none apart from requiring SSL by default again [Other Info] * As being said, nagios-nrpe-server is currently unusable in its current state IFF using an older OS release as nagios master. The only option is to either pin nagios-nrpe-server to xenial (effectively downgrading it) or disabling SSL altogether which seems equally bad :( ** Bug watch added: Debian Bug tracker #867567 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867567 ** Bug watch added: github.com/NagiosEnterprises/nrpe/issues #113 https://github.com/NagiosEnterprises/nrpe/issues/113 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720029 Title: Backport "Re-enable SSL support by default. Compatibility with older versions has been fixed." to zesty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1720029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
