Hello,
When noscript is activated, the about:config key network.protocol-handler.expose.ed2k is reset to "true" at each firefox start.
What can i do to fix it to "false" ?
Thanks for your help
NoScript resets a specific config key
-
FM33
NoScript resets a specific config key
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0
- Giorgio Maone
- Site Admin
- Posts: 9557
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: NoScript resets a specific config key
This is part of a protection against cross-application attacks which exploit URI missing or wrong sanitization by other applications.
You can disable it by setting the noscript.fixURI about:config preference to false.
You can disable it by setting the noscript.fixURI about:config preference to false.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0
-
FM33
Re: NoScript resets a specific config key
Thanks, it worked
I pointed out noscript.fixURI.exclude key. I tried first setting "ed2k" as value, but it didn't work. What is the way to use this exclude list to avoid disabling completely this protection ?
I pointed out noscript.fixURI.exclude key. I tried first setting "ed2k" as value, but it didn't work. What is the way to use this exclude list to avoid disabling completely this protection ?
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0
- Giorgio Maone
- Site Admin
- Posts: 9557
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: NoScript resets a specific config key
You can't.FM33 wrote:What is the way to use this exclude list to avoid disabling completely this protection ?
Could you explain me what does not work for you with network.protocol-handler.expose.ed2k set to false?
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0
-
FM33
Re: NoScript resets a specific config key
Actually, the wanted value is "false". When it is set to "true", FF won't open ed2k:// links. In fact, it doesn't work either, but it's probably a FF and/or Ubuntu issue. Fixing the value to false is a first step before asking for more help with protocol handling.Giorgio Maone wrote:You can't.FM33 wrote:What is the way to use this exclude list to avoid disabling completely this protection ?
Could you explain me what does not work for you with network.protocol-handler.expose.ed2k set to false?
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0