{"id":23725,"date":"2022-03-19T18:58:15","date_gmt":"2022-03-19T17:58:15","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=23725"},"modified":"2023-03-13T05:29:59","modified_gmt":"2023-03-13T04:29:59","slug":"firefox-blockiert-f-secure-browser-protection-add-on","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2022\/03\/19\/firefox-blockiert-f-secure-browser-protection-add-on\/","title":{"rendered":"Firefox blocks F-Secure Browser Protection Add-on"},"content":{"rendered":"<p><img loading=\"lazy\" decoding=\"async\" title=\"Firefox\" style=\"border-left-width: 0px; border-right-width: 0px; border-bottom-width: 0px; float: left; margin: 0px 10px 0px 0px; display: inline; border-top-width: 0px\" border=\"0\" alt=\"Mozilla\" src=\"https:\/\/i.imgur.com\/Dhputf4.jpg\" width=\"65\" align=\"left\" height=\"63\"><\/a>[<a href=\"https:\/\/www.borncity.com\/blog\/2022\/03\/19\/firefox-blockiert-f-secure-browser-protection-add-on\/\" target=\"_blank\" rel=\"noopener\">German<\/a>]Brief information for users of the Firefox browser in Windows, who also have the F-Secure antivirus solution in use. Since March 18, 2022, the browser has blocked the F-Secure Browser Protection add-on in versions up to 4.0.52, allegedly for violating Mozilla's add-on guidelines.<\/p>\n<p><!--more--><\/p>\n<h2>A reader info<\/h2>\n<p><img loading=\"lazy\" decoding=\"async\" alt=\"\" src=\"https:\/\/vg02.met.vgwort.de\/na\/8d06fbce150b4b1d9f0cad0a69a2f6a5\" width=\"1\" height=\"1\">It was a short message from a German blog reader reader via Facebook that reached me today &#8211; I'm only now getting around to briefly rehashing it. The relevant text of the message was:<\/p>\n<blockquote>\n<p>Do you know anything about Firefox rejecting the F-secure add-on? I have F-Secure on my laptop. <\/p>\n<\/blockquote>\n<p><a href=\"https:\/\/i.imgur.com\/SJoIytW.png\" target=\"_blank\" rel=\"noopener\"><img loading=\"lazy\" decoding=\"async\" title=\"Firefox blockiert F-Secure Browser Protection Add-on\" alt=\"Firefox blockiert F-Secure Browser Protection Add-on\" src=\"https:\/\/i.imgur.com\/SJoIytW.png\" width=\"671\" height=\"352\"><\/a><br \/>Click to zoom<\/p>\n<p>Included was the screenshot above showing the Firefox display. The user is informed that the Firefox browser add-on \"Browsing Protection by F-Secure\" has been disabled to protect the user. The reason given is that the add-on violates Mozilla's add-on policy. The Firefox browser then disables the add-on automatically. In the screenshot above, you can see that the disabling occurred on March 18, 2022 and is valid until version 4.0.52. From this I conclude that the add-on was accepted by Firefox before that date.<\/p>\n<h2>Entries in the F-Secure forum<\/h2>\n<p>I did some quick research and found what I was looking for in the F-Secure forums, for example in <a href=\"https:\/\/community.f-secure.com\/en\/discussion\/125034\/mozilla-firefox-blocking-browsing-protection-by-f-secure-addon\" target=\"_blank\" rel=\"noopener\">this thread<\/a>. With date March 18, 2022, another user reports that the Firefox browser add-on \"Browsing Protection by F-Secure\" has been disabled:<\/p>\n<blockquote>\n<p>Mozilla Firefox blocking Browsing Protection by F-Secure addon<\/p>\n<p>I had the F-Secure addon (version 3.0.27) installed and today Mozilla blocked and disabled it, stating:  <\/p>\n<p>=========================================================  <\/p>\n<p>\"Browsing Protection by F-Secure has been blocked for your protection.  <\/p>\n<h4>Why was it blocked?<\/h4>\n<p>This add-on violates Mozilla's Add-on Policies.  <\/p>\n<p>This add-on violates Mozilla's add-on policies by executing remote code and insufficient user data handling and protections.  <\/p>\n<h4>What does this mean?<\/h4>\n<p>The problematic add-on or plugin will be automatically disabled and no longer usable.  <\/p>\n<p>When Mozilla becomes aware of add-ons, plugins, or other third-party software that seriously compromises Firefox security, stability, or performance and meets certain criteria, the software may be blocked from general use. For more information, please read this support article.  <\/p>\n<p>Versions blocked: 0 to 4.0.52.  <\/p>\n<p>Blocked on Mar 18, 2022.<\/p>\n<\/blockquote>\n<p><img loading=\"lazy\" decoding=\"async\" title=\"Firefox blocks F-Secure Browser Protection Add-on\" alt=\"Firefox blocks F-Secure Browser Protection Add-on\" src=\"https:\/\/i.imgur.com\/n2NA5xw.png\" width=\"618\" height=\"128\">  <\/p>\n<p>In the thread there are confirmations of further affected persons &#8211; further hits are <a href=\"https:\/\/community.f-secure.com\/en\/discussion\/125040\/why-has-mozilla-firefox-blocked-browsing-protection-by-f-secure-add-on\" target=\"_blank\" rel=\"noopener\">here<\/a>, <a href=\"https:\/\/community.f-secure.com\/en\/discussion\/125037\/mozilla-just-blocked-f-secure-extension\" target=\"_blank\" rel=\"noopener\">here<\/a> and <a href=\"https:\/\/web.archive.org\/web\/20220322112054\/https:\/\/malwaretips.com\/threads\/browsing-protection-by-f-secure-blocked-by-firefox.112879\/\" target=\"_blank\" rel=\"noopener\">here<\/a>. And it doesn't seem to have been the first occurrence (<a href=\"https:\/\/web.archive.org\/web\/20221005001314\/https:\/\/community.f-secure.com\/safe-en\/kb\/articles\/9127-firefox-blocked-or-disabled-browsing-protection-extension-with-the-following-error-message-could-not-be-verified-for-use-in-firefox-and-has-been-disabled\" target=\"_blank\" rel=\"noopener\">here's<\/a> an entry from 2021).&nbsp; <\/p>\n<h2>F-Secure is aware of the issue<\/h2>\n<p>In the meantime, an F-Secure moderator has <a href=\"https:\/\/community.f-secure.com\/en\/discussion\/comment\/129183\/#Comment_129183\" target=\"_blank\" rel=\"noopener\">written in the forum<\/a> that the problem is known. They are working with Mozilla to find a solution: <\/p>\n<blockquote>\n<p>Hi @mrxfsec @needsomeusername @radetzky @ruudvl @MagDux @Ronnie74 @Beecee @Flockle  <\/p>\n<p>We are aware of this issue on the Windows version of our consumer and corporate EPP products.  <\/p>\n<p>We are currently working with Mozilla to solve this issue. Meanwhile, we recommend that you use either Microsoft Edge or Google Chrome browser<strong> <\/strong>until the issue has been fixed.  <\/p>\n<p>We already published a KB article about this issue and you can <a href=\"https:\/\/web.archive.org\/web\/20220318165556\/https:\/\/community.f-secure.com\/safe-en\/kb\/articles\/9259\" target=\"_blank\" rel=\"noopener\">read more here<\/a>&nbsp; <\/p>\n<p>You can subscribe to our <a href=\"https:\/\/status.f-secure.com\/\" target=\"_blank\" rel=\"noopener\">Status page<\/a> to get notified on incident reports and when they get resolved.  <\/p>\n<p>Thanks for your patience and understanding.<\/p>\n<\/blockquote>\n<p>The <a href=\"https:\/\/web.archive.org\/web\/20220318165556\/https:\/\/community.f-secure.com\/safe-en\/kb\/articles\/9259\" target=\"_blank\" rel=\"noopener\">KB article<\/a> states that the problem with Firefox occurs only on Windows when using the following F-Secure products:  <\/p>\n<ul>\n<li>F-Secure Home products: F-Secure TOTAL, F-Secure SAFE, and F-Secure Internet Security\n<li>F-Secure Business products: F-Secure Elements Endpoint Protection, F-Secure Elements EPP for Computers, F-Secure Elements EPP for Servers, F-Secure Client Security, F-Secure Server Security<\/li>\n<\/ul>\n<p>The browser extension is a plug-in application that ensures the user's security while browsing. The Browsing Protection extension is currently not available for Mozilla Firefox. For this reason, the Safe Browsing and Banking features do not fully work when using the Firefox browser at the moment. F-Secure says it is working with Mozilla to resolve this issue. In the meantime, the F-Secure folks recommend users to use either Microsoft Edge or Google Chrome until the issue is resolved.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[German]Brief information for users of the Firefox browser in Windows, who also have the F-Secure antivirus solution in use. Since March 18, 2022, the browser has blocked the F-Secure Browser Protection add-on in versions up to 4.0.52, allegedly for violating &hellip; <a href=\"https:\/\/borncity.com\/win\/2022\/03\/19\/firefox-blockiert-f-secure-browser-protection-add-on\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[872,463,2],"tags":[2716,2715,530,47],"class_list":["post-23725","post","type-post","status-publish","format-standard","hentry","category-browser","category-issue","category-windows","tag-add-on","tag-f-secure","tag-firefox","tag-issue"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/23725","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=23725"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/23725\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=23725"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=23725"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=23725"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}