> From: Juan Lang
> Ha, right you are. Hm. Well, a wireshark capture of the connection
> might help, to verify that the web server is in fact attaching the
> correct certificate to the connection in the IPv6 case.
The URL in question is actually https://testbot.winehq.org/. Browsing
there using
> That's going to be a bit of a problem. The tests fail on Windows, haven't
> found a way yet to convince the Windows DLLs to produce trace logs...
Ha, right you are. Hm. Well, a wireshark capture of the connection
might help, to verify that the web server is in fact attaching the
correct certif
> From: Juan Lang [mailto:juan.l...@gmail.com]
> > Sorry, haven't had the time to investigate yet (only looked up the
> > error code which is ERROR_INTERNET_SEC_CERT_CN_INVALID).
>
> That would imply that the certificate checking is failing. Please get
> a +crypt,+chain log of the failing tests an
> Sorry, haven't had the time to investigate yet (only looked up the error code
> which is
> ERROR_INTERNET_SEC_CERT_CN_INVALID).
That would imply that the certificate checking is failing. Please get
a +crypt,+chain log of the failing tests and attach to a bug for me to
have a look.
--Juan
> From: Austin Lund
> On 14 November 2010 07:40, Greg Geldorp wrote:
> > Hi,
> >
> > All TestBot VMs (with the exception of the Win9x ones) now have IPv6
> > connectivity. I was surprised that there was even a IPv6 stack available
> > for NT4, it was produced by Microsoft Research.
> > The VMs are
On 14 November 2010 07:40, Greg Geldorp wrote:
> Hi,
>
> All TestBot VMs (with the exception of the Win9x ones) now have IPv6
> connectivity. I was surprised that there was even a IPv6 stack available for
> NT4, it was produced by Microsoft Research.
> The VMs are (and always have been) behind a
