Bug#770349: ldirectord: SSL hostname check failure

2014-11-20 Thread Shawn Heisey
Package: ldirectord Version: 1.0.3-4 When ldirectord does https health checks, they fail because newer LWP versions validate the hostname used against the hostname in the certificate, and ldirectord is almost always configured with IP addresses. The simple fix for this is here:

Bug#770349: ldirectord: SSL hostname check failure

2014-11-20 Thread Kurt Roeckx
On Thu, Nov 20, 2014 at 09:43:02AM -0700, Shawn Heisey wrote: Package: ldirectord Version: 1.0.3-4 When ldirectord does https health checks, they fail because newer LWP versions validate the hostname used against the hostname in the certificate, and ldirectord is almost always configured

Bug#770349: ldirectord: SSL hostname check failure

2014-11-20 Thread Shawn Heisey
On 11/20/2014 12:22 PM, Kurt Roeckx wrote: This fix is just plain wrong and you might as well stop using HTTPS in that case. Please fix the certificate instead. It can contain IP addresses just as well as hostnames. It's recommended to use the SubjectAltName, but you can put it in the CN

Bug#770349: ldirectord: SSL hostname check failure

2014-11-20 Thread Salvatore Bonaccorso
Hi, On Thu, Nov 20, 2014 at 09:43:02AM -0700, Shawn Heisey wrote: Package: ldirectord Version: 1.0.3-4 When ldirectord does https health checks, they fail because newer LWP versions validate the hostname used against the hostname in the certificate, and ldirectord is almost always

Bug#770349: ldirectord: SSL hostname check failure

2014-11-20 Thread Shawn Heisey
On 11/20/2014 1:59 PM, Salvatore Bonaccorso wrote: Note that this is #739608, and already fixed both in wheezy and jessie. Thanks for the info. The problem remains in Ubuntu 14, should I file a bug against their package? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#770349: ldirectord: SSL hostname check failure

2014-11-20 Thread Salvatore Bonaccorso
Hi, On Thu, Nov 20, 2014 at 02:21:18PM -0700, Shawn Heisey wrote: On 11/20/2014 1:59 PM, Salvatore Bonaccorso wrote: Note that this is #739608, and already fixed both in wheezy and jessie. Thanks for the info. The problem remains in Ubuntu 14, should I file a bug against their package?