Search results
From GreaseSpot Wiki
Jump to navigationJump to search
Page title matches
- 2 KB (266 words) - 03:17, 22 March 2012
Page text matches
- ...obvious to me what the distinction is between this page and the [[Security tips]] page. Should the pages be merged? If not, could it be made more clear wha ...model. For tips you can apply directly to your scripts, see '''[[Security tips]]'''." That's the distinction, though one could still argue that they shoul ...673 bytes (100 words) - 13:23, 22 March 2012
- ...semonkey [[sandbox]], with its use of [[XPCNativeWrappers]] guarantees the security of the advanced capabilities a user script has from the potentially malicio Also, this security is guaranteed only if the script does not break the security model; dangerous tools like [[unsafeWindow]] are provided to authors in the ...4 members (0 subcategories, 0 files) - 16:59, 4 February 2010
- ...model. For tips you can apply directly to your scripts, see '''[[Security tips]]'''. ...http://mozdev.org/pipermail/greasemonkey/2005-July/004022.html described a security flaw] with this design, on July 19th 2005, while [[Greasemonkey]] was at [[ ...3 KB (474 words) - 20:02, 3 November 2017
- {{security}} unsafeWindow bypasses [[Greasemonkey]]'s security model, which exists to make sure that malicious web pages cannot alter obje ...2 KB (217 words) - 14:15, 11 March 2023
- ...ed a known [https://www.mozilla.org/en-US/security/advisories/mfsa2015-78/ security vulnerability]. [[Category:Coding Tips:Interacting With The Page]] ...746 bytes (115 words) - 15:54, 23 September 2015
- * [[Security]] * [[:Category:Coding Tips]] ...962 bytes (137 words) - 16:43, 3 November 2017
