Signing of closed source binary extension

Hello,

Apparently we need to get our XPI signed for use with newer Firefox versions. Our extension is binary and closed source - what options do we have?

We gave up submitting for listing a long time ago due to the requirement of submitting our full source base. So I had hoped the little check box “don’t list” would make it possible to get the XPI signed somehow anyway when submitting the XPI for review. But no, I get the following message:

“Any code which bundles native binaries must submit full source code, and undergo manual code review for at least one submission.”

Isn’t there some way to waive this requirement? I mean, do you really get the full source code from, say, Kaspersky labs or whoever else makes binary closed source extensions?

Thanks for any clarification!

Ulrik

Yes, they do. All anti-virus companies, and actually all uploaders have to do so. I believe that only admins can see the source code, but @TheOne who would most likely be The One to review you if you upload to the unlisted queue can tell you more.

Exactly., though I am thankfully not the only one anymore reviewing unlisted add-ons.