InformAction Forums

This isn't specifically a NS problem, and I haven't verified it yet. But at the moment, my copies of FF 3.6.28 are unable to verify any signed add-ins.

I only mention it because I wonder if, what with the changes to signing, the process used by FF 3.6.28 may not be supported anymore?

In which case, you may wish to add to the download page another line about legacy versions.

Thanks for reporting this. Technically 3.6.28 is supported by Giorgio, but as it hasn't been supported by Mozilla in a long time, I can't recommend using it - especially if you're concerned enough about security to use NoScript.

What kind of failure are you seeing? Any specific error message(s)?

because signing could not be verified.-260

This is likely not the issue:

http://forums.mozillazine.org/viewtopic ... 8&t=597317

But something along these lines most likely is:

http://microdevsys.com/wp/firefox-firef ... -verified/


I suppose basically you're attempting to use an outdated program that uses now outdated methods (ciphers) when dealing with current extensions.

Remove the META-INF directory from the xpi & it will install successfully.
(Operation could be a different matter.)

Other then "piece of mind" - of the extension itself, signing serves no purpose in something that old. And given you're using something that old anyhow, its kind of contradictory.

Can someone out there make this easier for us? Can you tell us which certificate this install uses? Wouldn't the suggestion at microdevsys.com then work if we changed the appropriate certificate setting in FF to "This certificate can identify software makers" as suggested? (Obviously I have encountered the same problem...)

If you really can't update Firefox (which would certainly be my recommendation) or switch to another browser, then you may as well just remove the META-INF directory from the extension.
Obviously you have a very restricted environment, and extension signing is not likely to give you much value.