On Mon, Dec 23, 2013 at 2:04 PM, Lars Ellenberg
<[email protected]>wrote:

> On Fri, Dec 20, 2013 at 12:31:05PM +0100, Timur I. Bakeyev wrote:
> > > So maybe exporting PERL_LWP_SSL_VERIFY_HOSTNAME=0 somewhere
> > > is the more elegant solution?
> > >
> >
> >
> > That was my original idea, but playing with ENV variables within
> ldirectord
> > sounds a bit dangerous. We can play with $ua->ssl_opts( $key => $value );
> > instead.
> >
> > Not sure, if it exists in the previous versions of LWP, so, possibly,
> have
> > to be verified with 'can' call.
> >
> > Also, it seems, that similar code was committed to the repository 2
> months
> > ago:
> >
> https://github.com/ClusterLabs/resource-agents/commit/b4bb7444455ec4fcfb2c5900282d81f9fa88bf86
>
> In that case, your issue 361 does no longer apply,
> because already fixed, right?
>


I guess so. Thanks to Mori-san for pointing onto this.


>
> And we could wait for the next issue complaining about too noisy
> warnings on older LWP versions.
>

Let's hope they'll upgrade :)
_______________________________________________________
Linux-HA-Dev: [email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Reply via email to