On Fri, 19 Feb 2016 23:01:24 -0500 Simon Ruggier <
simon80@gmail.com> wrote:
> Also, my own testing seems to show that the certificate chain issue is
> still present in the latest 1.0.1 release (as I commented on 813468), so
> adopting the latest 1.0.2 release seems like the only reasonable
> alternative.
As I commented in bug #813468, it turns out that I hadn't tested this correctly, and the latest 1.0.1 release does, in fact, fix this issue.