The simplest and most drastic change would be to open up
mozilla/caps/src/nsScriptSecurityManager, and make the
CheckPropertyAccessImpl function a no-op that always returns true. That
will essentially disable all security and create a browser that's
totally unsafe to be used on the public
hocus, I think such measures are an extremely bad idea. On the internet,
you cannot trust that
* a certain host is the one you think it is (esp. so with HTTP and
in some cases even with HTTPS)
* that the data you receive is unaltered (with HTTP)
Giving any http host on the
Ben Bucksch wrote:
hocus, I think such measures are an extremely bad idea. On the internet,
you cannot trust that
Did he say he was doing this on the internet?
I request that the trunk builds allow the user to disable the fix for bug
154930, as was done in the 1.0 branch. The fix for bug 154930 is causing
major problems with Yahoo mail (see bug 160339). According to the bugzilla
comments regarding bug 154930, the current fix has caused signficant
Matthew Seitz wrote:
I request that the trunk builds allow the user to disable the fix for bug
154930, as was done in the 1.0 branch.
As far as that goes, I'd like to request that this bug be added to
http://mozilla.org/projects/security/known-vulnerabilities.html, since
this is a publicly
Matthew Seitz [EMAIL PROTECTED] wrote in message
akmjct$[EMAIL PROTECTED]">news:akmjct$[EMAIL PROTECTED]...
I request that the trunk builds allow the user to disable the fix for bug
154930, as was done in the 1.0 branch. The fix for bug 154930 is causing
major problems with Yahoo mail (see
