Closed
Bug 182566
Opened 23 years ago
Closed 20 years ago
Can't access signed scripts after refresh
Categories
(Core :: Security, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: ygoraly, Assigned: security-bugs)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126
After loaded for the first time, I can access singed scripts from a non signed
page. Once I refresh the broser, I can't access them any more - get Error:
uncaught exception: Permission denied to get property...
The signed section of the application works fine within itself.
I am using a test certificate
Reproducible: Always
Steps to Reproduce:
1.load an application that has both non signed and signed pages
2.Refresh the broser (F5)
3.Try to access signed script from the non signed script
Actual Results:
Error: uncaught exception: Permission denied to get property ...
Expected Results:
Execute the script, like before refresh
| Reporter | ||
Comment 1•23 years ago
|
||
Fixing this bug is very important, since the end user of the application will
not know why things are not working any more and will stop using the application
altogether.
Comment 2•22 years ago
|
||
Why is this in search component? I don't think it has to do anything with it.
Over to
-> JavaScript engine
(not sure about that but it has something to do with scripting and security)
Component: Search → JavaScript Engine
Comment 3•22 years ago
|
||
---> Security:General
Assignee: sgehani → mstoltz
Component: JavaScript Engine → Security: General
QA Contact: claudius → bsharma
| Assignee | ||
Comment 4•22 years ago
|
||
I'll take a look.
Comment 5•20 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 6•20 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•