Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Remove Google search bar from about:newtab page

  • 4 wotmołwy
  • 28 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot vtwiins

more options

This is maddening, and why users DON'T upgrade their software. The last 3 Firefox updates have caused many https sites to fail to open in Firefox, but they work fine in IE. Lowering the TLS settings in about:config from 3 to 2 fixed it prior to version 31.0

When that failed to fix it today after upgrading again, I became suspicious of Kaspersky and disabled it which resolved the https issue. I'm still confused on why upgrading Firefox has resulted in Kaspersky blocking the application for suspicious activity though. I believe it is either connected to strange/unexpected uses of DNS or proxy server settings.

To add insult to injury, I now have a highly UNDESIREABLE Google search bar across the top of my about:newtab page in version 31.0. Why? Who thought this was a good idea at Mozilla?

If I wanted Google (or any other search engine) to see every search query I enter, I would set that search engine as my homepage, or drop Mozilla completely and use Chrome. When the Mozilla developers add such unwanted code to their browser, they are in essence removing the attractiveness of using it in the first place. Today is a loss as I spent the whole day messing with this.

Again, this is why people DON'T UPGRADE - This "upgrade" has screwed up my browser just as much as any virus ever has. </end rant>

This is maddening, and why users DON'T upgrade their software. The last 3 Firefox updates have caused many https sites to fail to open in Firefox, but they work fine in IE. Lowering the TLS settings in about:config from 3 to 2 fixed it prior to version 31.0 When that failed to fix it today after upgrading again, I became suspicious of Kaspersky and disabled it which resolved the https issue. I'm still confused on why upgrading Firefox has resulted in Kaspersky blocking the application for suspicious activity though. I believe it is either connected to strange/unexpected uses of DNS or proxy server settings. To add insult to injury, I now have a highly UNDESIREABLE Google search bar across the top of my about:newtab page in version 31.0. Why? Who thought this was a good idea at Mozilla? If I wanted Google (or any other search engine) to see every search query I enter, I would set that search engine as my homepage, or drop Mozilla completely and use Chrome. When the Mozilla developers add such unwanted code to their browser, they are in essence removing the attractiveness of using it in the first place. Today is a loss as I spent the whole day messing with this. Again, this is why people DON'T UPGRADE - This "upgrade" has screwed up my browser just as much as any virus ever has. </end rant>

Wubrane rozrisanje

Thank you for the suggestions. I use the business version of Kaspersky called Endpoint Security and after much digging I found a solution here: Kaspersky and Firefox SSL Bug

The fix requires submitting a support request for patch PT133 in KES 8.1.0.1042 - the previous version of KES 8 (v.8.1.0.831) must be upgraded before the patch can be installed.

As for the search bar, giving a box to tick or untick for this unwanted feature would be most diplomatic, but thanks for the workaround.

Tutu wotmołwu w konteksće čitać 👍 3

Wšě wotmołwy (4)

more options

(1) New Tab Page search bar

If you don't use the bar, then nothing is submitted to the search engine, it just sits there waiting...

You can suppress the display of this extra bar by applying a custom style rule to the page. There are a couple different ways to apply custom style rules in Firefox. Please see this thread for more information:

i have to remove the search engin option from the place where i am pining my favorite site links

If you would like to see some configuration options for the page, you can submit suggestions here: https://input.mozilla.org/feedback

(2) Kaspersky SSL Scan ("Scan Encrypted Connections")

You don't need to disable this feature if you like having Kaspersky intercept your secure connections for filtering. However, you need to set up Firefox to trust the fake certificates that Kaspersky presents to Firefox when you use this feature.

Here is some documentation that I've seen earlier this year, not sure it's the latest or matches your product exactly:

more options

Firefox as always is customisable so there are other things you could easily do. For instance

  • Pick another page to open as your own New Tab.
    I will not give full details here but the pref browser.newtab.url is set to about:newtab by default setting it to about:blank opens a blank page, or use any url you prefer.
  • Use whatever search bar you want.
    This is very easy. Just change the search engine selected in the searchbar to another preinstalled, or any search engine you wish. All other Firefox searches including the addressbar and newtab search bar also change.
more options

Issues with connecting to secure sites in Firefox 31 and later can be caused by switching to libPKIX.

You can test that by disabling libPKIX support in Firefox, but it is not recommended to leave it disabled on the long run for security and vulnerability reasons.

  • about:config page: security.use_mozillapkix_verification = false

It is possible that websites will correct this issue shortly, so make sure to check regularly if this workaround is still required by resetting the pref and see if you can connect. You may have to reload and bypass the cache via Ctrl+F5 after toggling this pref.

You can contact the website and bring this article under their attention. See "Behavior Changes" and "Things for CAs to Fix":


Add code to the userChrome.css file below the default @namespace line to hide the search bar on the new tab page.


@namespace url("https://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* only needed once */

@-moz-document url(about:newtab){
#newtab-margin-top, #newtab-search-container { display:none !important; }
}


The customization files userChrome.css (user interface) and userContent.css (websites) are located in the chrome folder in the Firefox profile folder.

You can use this button to go to the currently used Firefox profile folder:

  • Help > Troubleshooting Information > Profile Directory: Show Folder (Linux: Open Directory; Mac: Show in Finder)
  • Create the chrome folder (lowercase) in the <xxxxxxxx>.default profile folder if this folder doesn't exist
  • Use a plain text editor like Notepad to create a (new) userChrome.css file in the chrome folder (file name is case sensitive)
  • Paste the code in the userChrome.css file in the editor window
  • Make sure that the userChrome.css file starts with the default @namespace line
  • Make sure that you select "All files" and not "Text files" when you save the file via "Save file as" in the text editor as userChrome.css. Otherwise Windows may add a hidden .txt file extension and you end up with a not working userChrome.css.txt file
more options

Wubrane rozrisanje

Thank you for the suggestions. I use the business version of Kaspersky called Endpoint Security and after much digging I found a solution here: Kaspersky and Firefox SSL Bug

The fix requires submitting a support request for patch PT133 in KES 8.1.0.1042 - the previous version of KES 8 (v.8.1.0.831) must be upgraded before the patch can be installed.

As for the search bar, giving a box to tick or untick for this unwanted feature would be most diplomatic, but thanks for the workaround.