Security Manager vetoed action - Mozilla

This is a discussion on Security Manager vetoed action - Mozilla ; With FF3.0b5pre and Firebug 1.1.0b12 from http://getfirebug.com/releases the Firebug command line fails for simple expressions like "var a;". The message is new and I don't know what to do with it: commandLine.evaluate FAILS: [Exception... "Security Manager vetoed action" nsresult: "0x80570027 ...

+ Reply to Thread
Results 1 to 10 of 10

Thread: Security Manager vetoed action

  1. Security Manager vetoed action

    With FF3.0b5pre and Firebug 1.1.0b12 from http://getfirebug.com/releases
    the Firebug command line fails for simple expressions like "var a;". The
    message is new and I don't know what to do with it:

    commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    action" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    location: "JS frame :: chrome://firebug/content/commandLine.js ::
    :: line 100" data: no]
    with (__win__.__scope__.vars) { with (__win__.__scope__.api) { with
    (__win__.__scope__.userVars) { with (__win__) {try
    {__win__.__scope__.callback(eval(__win__.__scope__ .expr));} catch (exc)
    {__win__.__scope__.callback(exc, true);}}}}}
    Line 0

    Line 100 for commandLine.js is

    Components.utils.evalInSandbox(scriptToEval, sandbox);

    I've tried a several variations but so far I can't narrow it down. If I
    understood what the error message was trying to say it would help. Any
    hints? (The code works in FF3b4 and FF2).

    John.

  2. Re: Security Manager vetoed action

    On Wed, Mar 19, 2008 at 11:56 AM, John J. Barton
    wrote:
    > With FF3.0b5pre and Firebug 1.1.0b12 from http://getfirebug.com/releases
    > the Firebug command line fails for simple expressions like "var a;". The
    > message is new and I don't know what to do with it:
    >
    > commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    > action" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    > location: "JS frame :: chrome://firebug/content/commandLine.js ::
    > :: line 100" data: no]
    > with (__win__.__scope__.vars) { with (__win__.__scope__.api) { with
    > (__win__.__scope__.userVars) { with (__win__) {try
    > {__win__.__scope__.callback(eval(__win__.__scope__ .expr));} catch (exc)
    > {__win__.__scope__.callback(exc, true);}}}}}
    > Line 0
    >
    > Line 100 for commandLine.js is
    >
    > Components.utils.evalInSandbox(scriptToEval, sandbox);
    >
    > I've tried a several variations but so far I can't narrow it down. If I
    > understood what the error message was trying to say it would help. Any
    > hints? (The code works in FF3b4 and FF2).


    I'm not sure exactly what causes that, though I hope to have some time
    to look at it and some related issues today. If there isn't a
    specific bug about this (or any other Firebug-affecting regression
    between b4 and b5), please file one so we can see if it makes sense to
    block the beta.

    Mike

  3. Re: Security Manager vetoed action

    On Mar 20, 1:56 am, "John J. Barton"
    wrote:
    > With FF3.0b5pre and Firebug 1.1.0b12 fromhttp://getfirebug.com/releases
    > the Firebug command line fails for simple expressions like "var a;". The
    > message is new and I don't know what to do with it:
    >
    > commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    > action" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    > location: "JS frame :: chrome://firebug/content/commandLine.js ::
    > :: line 100" data: no]
    > with (__win__.__scope__.vars) { with (__win__.__scope__.api) { with
    > (__win__.__scope__.userVars) { with (__win__) {try
    > {__win__.__scope__.callback(eval(__win__.__scope__ .expr));} catch (exc)
    > {__win__.__scope__.callback(exc, true);}}}}}
    > Line 0
    >
    > Line 100 for commandLine.js is
    >
    > Components.utils.evalInSandbox(scriptToEval, sandbox);
    >
    > I've tried a several variations but so far I can't narrow it down. If I
    > understood what the error message was trying to say it would help. Any
    > hints? (The code works in FF3b4 and FF2).
    >
    > John.


    The code fails in FF2.0.0.13 for me with FB1.1.0b12. I liked being
    able to execute random code there before!

    Peter

  4. Re: Security Manager vetoed action

    I'm getting something similar when I use the console for FF3b5:

    $("form").submit();

    commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    action" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    location: "JS frame :: chrome://firebug/content/commandLine.js ::
    :: line 100" data: no]
    with (__win__.__scope__.vars) { with (__win__.__scope__.api) { with
    (__win__.__scope__.userVars) { with (__win__) {try
    {__win__.__scope__.callback(eval(__win__.__scope__ .expr));} catch
    (exc) {__win__.__scope__.callback(exc, true);}}}}}
    Line 0

    Even if I add '$' to the watch, I get the same error.


  5. Re: Security Manager vetoed action

    starmonkey wrote:
    > I'm getting something similar when I use the console for FF3b5:
    >
    > $("form").submit();
    >
    > commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    > action" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    > location: "JS frame :: chrome://firebug/content/commandLine.js ::
    > :: line 100" data: no]
    > with (__win__.__scope__.vars) { with (__win__.__scope__.api) { with
    > (__win__.__scope__.userVars) { with (__win__) {try
    > {__win__.__scope__.callback(eval(__win__.__scope__ .expr));} catch
    > (exc) {__win__.__scope__.callback(exc, true);}}}}}
    > Line 0
    >
    > Even if I add '$' to the watch, I get the same error.
    >

    This will be fixed in Firebug 1.2a12X in a couple of days.

  6. Re: Security Manager vetoed action

    On Apr 2, 9:53*pm, "John J. Barton"
    wrote:
    > starmonkey wrote:
    > > I'm getting something similar when I use the console for FF3b5:

    >
    > > $("form").submit();

    >
    > > commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    > > action" *nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    > > location: "JS frame :: chrome://firebug/content/commandLine.js ::
    > > :: line 100" *data: no]
    > > with (__win__.__scope__.vars) { with (__win__.__scope__.api) { with
    > > (__win__.__scope__.userVars) { with (__win__) {try
    > > {__win__.__scope__.callback(eval(__win__.__scope__ .expr));} catch
    > > (exc) {__win__.__scope__.callback(exc, true);}}}}}
    > > Line 0

    >
    > > Even if I add '$' to the watch, I get the same error.

    >
    > This will be fixed in Firebug 1.2a12X in a couple of days.


    Any update?

  7. Re: Security Manager vetoed action

    Gary King wrote:
    > On Apr 2, 9:53 pm, "John J. Barton"
    > wrote:
    >> starmonkey wrote:
    >>> I'm getting something similar when I use the console for FF3b5:
    >>> $("form").submit();
    >>> commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    >>> action" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    >>> location: "JS frame :: chrome://firebug/content/commandLine.js ::
    >>> :: line 100" data: no]
    >>> with (__win__.__scope__.vars) { with (__win__.__scope__.api) { with
    >>> (__win__.__scope__.userVars) { with (__win__) {try
    >>> {__win__.__scope__.callback(eval(__win__.__scope__ .expr));} catch
    >>> (exc) {__win__.__scope__.callback(exc, true);}}}}}
    >>> Line 0
    >>> Even if I add '$' to the watch, I get the same error.

    >> This will be fixed in Firebug 1.2a12X in a couple of days.

    >
    > Any update?


    http://getfirebug.com/releases
    has Firebug 1.2a13X (alpha 13 with tracing options)
    commandline works except for special command line API.

    John.

  8. Re: Security Manager vetoed action



    I'm getting something similar when I use the console for FF3b5:
    alert(1):
    commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    action" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    location: "JS frame :: chrome://firebug/content/commandLine.js ::
    :: line 100" data: no]

  9. Re: Security Manager vetoed action

    bear wrote:
    >
    > I'm getting something similar when I use the console for FF3b5:
    > alert(1):
    > commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    > action" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    > location: "JS frame :: chrome://firebug/content/commandLine.js ::
    > :: line 100" data: no]


    Firebug has its own newsgroup: http://groups.google.com/group/firebug
    and bug list: http://code.google.com/p/fbug/issues/list

    Firebug 1.1 does not work in FF3 after b4. We're concentrating on
    Firebug 1.2 for FF3.

  10. Re: Security Manager vetoed action

    On Apr 5, 5:46*am, John J Barton wrote:
    > Gary King wrote:
    > > On Apr 2, 9:53 pm, "John J. Barton"
    > > wrote:
    > >> starmonkey wrote:
    > >>> I'm getting something similar when I use the console for FF3b5:
    > >>> $("form").submit();
    > >>> commandLine.evaluate FAILS: [Exception... "Security Manager vetoed
    > >>> action" *nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)"
    > >>> location: "JS frame :: chrome://firebug/content/commandLine.js ::
    > >>> :: line 100" *data: no]
    > >>> with (__win__.__scope__.vars) { with (__win__.__scope__.api) { with
    > >>> (__win__.__scope__.userVars) { with (__win__) {try
    > >>> {__win__.__scope__.callback(eval(__win__.__scope__ .expr));} catch
    > >>> (exc) {__win__.__scope__.callback(exc, true);}}}}}
    > >>> Line 0
    > >>> Even if I add '$' to the watch, I get the same error.
    > >> This will be fixed in Firebug 1.2a12X in a couple of days.

    >
    > > Any update?

    >
    > http://getfirebug.com/releases
    > has Firebug 1.2a13X (alpha 13 with tracing options)
    > commandline works except for special command line API.
    >
    > John.


    its worked

+ Reply to Thread