Hi, On Thu, May 5, 2011 at 03:53, Gabriel M. Beddingfield <[email protected]> wrote: > On Wednesday, May 04, 2011 07:12:57 pm David Woodhouse > wrote: >> On Fri, 2011-04-29 at 12:22 +0200, Andre Klapper wrote: >> > Works fine. Whatever "can not work now" is meant to >> > mean, next time at least posting your error message >> > would be welcome. >> >> For me it seems to have an invalid (self-signed) >> certificate. Although I only noticed that just now; has >> it changed? > > I show that it it is certified by Go Daddy Secure > Certification Authority and has a SHA-1 hash of: > > B0 6A AD 46 F7 5D B4 7B 55 53 7A 8E 08 DA 69 FD 7B DC FB A5 > > (https://bugs.meego.com) There seem to be some misconfiguration of SSL setup at meego.com. I tried with QtWebkit and it also unable to reach and render it.
Looking into a network trace I can see that Firefox 4 talks TLSv1 to meego.com while QtWebkit uses SSLv3. When SSLv3 is used against meego.com, it responds: 4 0.222344 192.168.100.34 140.211.166.238 SSLv3 Client Hello 6 0.445039 140.211.166.238 192.168.100.34 SSLv3 Alert (Level:Fatal, Description: Handshake Failure) That's it, there is relatively little on the wire. I found this first when trying to debug RSS feed fetcher but it exhibits the same behavior with bugs.meego.com. -- / Alexander Bokovoy _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
