In theory there may be no significant increase in vulnerability, but Firefox created the signed add-on policy for a reason, I'm sure, which was probably because too many were not safe and causing problems. This has been a Firefox policy for some time, so I'm a bit surprised that Firebug has not been more proactive about getting this done. Thanks for the guestimated timeline for the update for this.
Wendy On Monday, May 16, 2016 at 3:49:05 PM UTC-4, Sebastian Zartner wrote: > > Until a few versions ago Firefox accepted extensions without requiring > them to be signed, so there's not more vulnerability than before. > Mozilla is trying to improve this situation by requiring extensions to be > signed now. The long-term solution will be Firebug 3, though I don't know > when that version will be released. I assume it will be together with > Firefox 48 in August. > > Sebastian > > On Monday, May 16, 2016 at 5:44:20 AM UTC+2, evdoor wrote: >> >> I just realized that I can't switch that config setting back without >> disabling Firebug. In order to keep Firebug active, I have to leave the >> signature.required setting at False. That sounds like it leaves my browser >> a bit vulnerable to unsigned and therefore potentially unsafe plugins and >> extensions. That doesn't sound like a good long-term solution. >> >> Is there a fix coming for this in Firebug that doesn't involve leaving my >> browser vulnerable? If so, how soon? >> >> >> On Friday, May 13, 2016 at 4:29:05 PM UTC-4, Sebastian Zartner wrote: >>> >>> After changing the setting, could you install it? If not, did you rename >>> the file extension to 'xpi' before dragging it into the Firefox window? >>> You can check whether the correct version is installed via the Firebug >>> menu > About... 2.0.1.6. In the opening dialog it should say >>> 2.0.16-issue8018 as version. >>> >>> Sebastian >>> >>> >>> On Friday, May 13, 2016 at 12:23:13 PM UTC+2, evdoor wrote: >>>> >>>> Hi Sebastian, >>>> >>>> I followed your instructions for issue #8018. Your fixed version of the >>>> plugin wouldn't install. So I changed the Firefox about:config setting you >>>> mentioned, but I still don't get the Computed attribute groups or Computed >>>> CSS source. Some of the CSS cascade steps also seem to be missing under >>>> the >>>> Style tab, which I think I've seen reported by others. As a result, I >>>> can't >>>> identify where a page is getting some of the styles. What else can I do to >>>> fix this? >>>> >>>> FYI: I have Firebug 2.0.16 on Firefox 46.0.1 on Windows 7. >>>> >>>> Many thanks in advance for the help. >>>> >>>> >>>> >>>> On Monday, May 2, 2016 at 2:16:52 AM UTC-4, Sebastian Zartner wrote: >>>>> >>>>> On Sunday, May 1, 2016 at 12:53:04 PM UTC+2, Michał Lepiarz wrote: >>>>>> >>>>>> After Firefox downgrade to 2.0.15 problem is fixed. >>>>>> >>>>> >>>>> Note that the issue is related to the Firefox version, not Firebug. >>>>> >>>>> >>>>>> Waiting for Firebug update... :) >>>>>> >>>>> >>>>> I've already fixed it (see issue #8018 >>>>> <https://github.com/firebug/firebug/issues/8018>). Now I hope there >>>>> will be a new version released soon. >>>>> >>>>> Sebastian >>>>> >>>>> W dniu niedziela, 1 maja 2016 09:10:51 UTC+2 użytkownik Michał Lepiarz >>>>>> napisał: >>>>>>> >>>>>>> Hello, >>>>>>> I've got problem with Computed styles display in newest Firebug >>>>>>> version (2.0.16 on Firefox 46). >>>>>>> I don't see localizations and I can't expand the definition >>>>>>> details. >>>>>>> >>>>>>> Below how it should looks like and how I see it. *Tried all options* >>>>>>> and nothing works. *Also options reset*. >>>>>>> >>>>>>> Can you please give me some tip how can I have it back? :) >>>>>>> >>>>>>> >>>>>>> <https://lh3.googleusercontent.com/-QVHRPmsCyIA/VySRLKwXk3I/AAAAAAAAH9E/XOmvRM8m8cwgZBo7PvVWF_55bENQOeaQQCLcB/s1600/Screenshot_1.jpg> >>>>>>> >>>>>>> <https://lh3.googleusercontent.com/-gf8rEBioG7Q/VySRA4gVKAI/AAAAAAAAH9A/UCc6ik2I6KYDTM8iuTLd5aJp-S8p5rjjACLcB/s1600/trace-styles.png> >>>>>>> >>>>>> -- You received this message because you are subscribed to the Google Groups "Firebug" group. To unsubscribe from this group and stop receiving emails from it, send an email to firebug+unsubscr...@googlegroups.com. To post to this group, send email to firebug@googlegroups.com. Visit this group at https://groups.google.com/group/firebug. To view this discussion on the web visit https://groups.google.com/d/msgid/firebug/99d4299d-edd3-4010-8fa4-c71d07153a09%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
