A fully signed extension is being reported as unsigned within Firefox 43?

Apologies in advance for posting this in multiple places, but I consider it quite urgent.

Apparently, quite a few of our users are seeing Firefox 43 disable our extension. A sample screenshot is at:

http://imgur.com/6mrlLLw

They’re running LastPass version 3.2.40, and the only version of 3.2.40 we’ve ever distributed is the one that was fully reviewed and signed on AMO. Thus, I don’t see how this could be possible, aside from a bug in Firefox.

This is already being handled on the addons-ux mailing list.