15 messages in org.mozilla.lists.dev-extensionsRe: FF3RC1: An error occurred while t...
FromSent OnAttachments
lega...@gmail.comMay 19, 2008 6:26 am 
John J. BartonMay 19, 2008 7:52 am 
Eric H. JungMay 19, 2008 9:58 am 
Dave TownsendMay 19, 2008 10:08 am 
lega...@gmail.comMay 19, 2008 10:43 pm 
MookMay 19, 2008 10:55 pm 
John J. BartonMay 20, 2008 7:22 am 
Mike ShaverMay 20, 2008 9:12 am 
Eric H. JungMay 20, 2008 9:14 am 
Nils MaierMay 20, 2008 11:20 am 
MookMay 22, 2008 9:49 pm 
Mike ShaverMay 23, 2008 7:52 am 
MookMay 26, 2008 4:35 am 
Demiao LinMay 27, 2008 1:47 am 
Eric H. JungMay 27, 2008 8:37 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: FF3RC1: An error occurred while trying to find updatesActions...
From:Nils Maier (Maie@web.de)
Date:May 20, 2008 11:20:57 am
List:org.mozilla.lists.dev-extensions

Mike Shaver wrote:

On Tue, May 20, 2008 at 1:55 AM, Mook <mook.moz+nntp@gmail.com> wrote:

Dave Townsend wrote:

lega@gmail.com wrote:

RDFItemUpdater::onXMLLoad: cert issuer is not built-in

That is the appropriate error, your ssl certificate must be signed by one of the built in CAs

Huh, not even for a properly user-installed CA? How would third-party distributors (think CCK-using large organizations deploying internally) be able to provide updates? Get a "real cert"?

Any known-to-the-browser CA should work; if you find that it doesn't, please file!

That's not the case, as Dave already mentioned. Only those from the built-in token (i.e. only directly compiled into the NSS db) will be accepted.[1] Same goes for Application AUS btw.

So even if your organization runs a proper local CA and the ca cert was installed into the certdb, even then you're out of luck.

Nils

http://mxr.mozilla.org/seamonkey/source/toolkit/mozapps/shared/src/badCertHandler.js#59