What happened to security.warn settings in about:config. They are missing in FF25. Please help!!
Hi,
I'm upgrading from Firefox 15 to Firefox 25. I used to be able to set the following security warnings in about:config.
security.warn_entering_secure security.warn_entering_weak security.warn_leaving_secure security.warn_submit_insecure security.warn_viewing_mixed
Not anymore. Looks like these are missing from Firefox 25. Please help!! Urgent.
Thank you. Sr.
Chosen solution
the warnings about entering/leaving a secure site are totally gone, you'd have to look out for the security indicator at the start of the address bar to get that information about a site: https://blog.mozilla.org/ux/2012/06/site-identity-ui-updates/
or use an extension like this one for better visibility: https://addons.mozilla.org/firefox/addon/safe/
the warning dialog about submitting data over an insecure channel at a secure site should still be in place...
Read this answer in context 👍 0All Replies (4)
hi iocl, those preferences were removed intentionally in firefox 19 & won't have an effect any longer - see bug #799009 (please don't post in bug reports).
please also update your plugins. your flash version is very out-dated & has security vulnerabilities that are actively exploited on the web.
Hi Philipp,
Thank you for the prompt response to my question. I have reviewed the comments in bug #799009.
Still, in Firefox 25, how is the user warned in the following scenarios:
1. When leaving a secure site 2. When entering a weak site 3. When submitting insecure data
Is there no warning to the users anymore?
Regards, iocl.
Chosen Solution
the warnings about entering/leaving a secure site are totally gone, you'd have to look out for the security indicator at the start of the address bar to get that information about a site: https://blog.mozilla.org/ux/2012/06/site-identity-ui-updates/
or use an extension like this one for better visibility: https://addons.mozilla.org/firefox/addon/safe/
the warning dialog about submitting data over an insecure channel at a secure site should still be in place...
See also:
- chrome://necko/locale/necko.properties
- chrome://pipnss/locale/security.properties