Le 11/05/2013 10:58, Jack Mitchell a écrit : >> In any case, there is a workaround on more recent b2g/gaia, with the fix >> for https://bugzilla.mozilla.org/show_bug.cgi?id=769178 : if you can >> browse to a website secured with this SSL cert, you'll be able to add an >> exception for it. And then it will be accepted by the whole Firefox OS. >> This workaround worked fine for me on the Firefox OS Simulator. >> Unfortunately, the Peak device currently runs an older version, which >> does not include this fix. > > Now that's interesting, as I tried this to no avail, I don't know if > downloading the certificates didn't work, but when I try to connect to > my imap I still get the message [bad-security]. > > I'm on a recent v1-train with the Keon. >
Is it the same certificate for the email and the web page? Except if it's a wildcard certificate, it has to be the same machine name, but you probably know that. In my case, it was for the calendar application, not the email : maybe they are not based on the same certificate list? The calendar application uses standard HTTP requests, whereas the email uses POP/IMAP/SMTP. I heard that, for the email application, they had to implement a TCP/IP stack on the Gecko engine. But I would find it surprising that they do not use the same certificates... _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
