DRM has some serious flaws RTSE out!

My First Bug

Filed in: Code, Firefox Add comments

That’s right! My first bug reported for Firefox, bug 331807.

The bug has to deal with a security error that isn’t an error in the current version of Firefox, but is an error in Bon Echo, the alpha release of Firefox 2.0. It’s a good thing that I test these things, as that would have been a big monkey wrench once 2.0 came out. I’ve found a workaround for it, but I fear that the workaround leaves the same security hole open that was patched in Bon Echo.

Regrettably, it also happens to be bug that kills the main feature of my most popular extension, RTSE. It will also kill the main feature in an extension I’ve been planning to make. Can we say ‘Curses’ anyone? Of course, this won’t affect Firefox 1.5.0.*, so those of you who uses the stable builds of Firefox will have nothing to worry about for some time.

I’ll keep updating this in the comments for anyone that is interested.

7 Responses to “My First Bug”

  1. Shawn Wilsher Says:
    March 30th, 2006 at 11:43 (11:43 am)

    Yeah - I don’t have a workaround. I’m not sure how I thought I did in the first place. Hopefully there will be more updates to follow.

  2. goatman93 Says:
    March 30th, 2006 at 15:49 (3:49 pm)

    https://addons.mozilla.org/extensions/moreinfo.php?application=firefox&id=958
    There is the nightly tester tools. Once it gets ported to Bon Echo, RTSE should be fine. :)

  3. Shawn Wilsher Says:
    March 30th, 2006 at 16:43 (4:43 pm)

    @goatman93
    Well, it happens to be more complicated than just the version number sadly. It’s a big security error, but I’m working hard to figure out how to get it to work.

  4. Reed Says:
    March 30th, 2006 at 18:01 (6:01 pm)

    So is it an intentional “error”, or a bug that can be expected to be fixed prior to the public release?

  5. Shawn Wilsher Says:
    March 30th, 2006 at 18:21 (6:21 pm)

    @Reed
    Well, it their eye’s they patched a potential security hole. In my eyes, it’s killing the extension. So chances are I need to come up with a workaround, but if there isn’t one, I’m going to be lobbying for the patch that was added to be backed out.

  6. Shawn Wilsher Says:
    March 31st, 2006 at 00:04 (12:04 am)

    Update:
    It looks as though we’ve come up with a workaround. This however may be a security hole, so I’ll keep on this.

  7. Shawn Wilsher Says:
    March 31st, 2006 at 07:50 (7:50 am)

    Update:
    RESOLVED, WONTFIX
    With the workaround, it doesn’t matter anyway.