Persona is no longer an option for authentication on BMO. For more details see Persona Deprecated.
Last Comment Bug 729614 - Softblock McAfee Site Advisor versions <
: Softblock McAfee Site Advisor versions <
Product: Toolkit
Classification: Components
Component: Blocklisting (show other bugs)
: unspecified
: All All
: -- normal (vote)
: ---
Assigned To: Jorge Villalobos [:jorgev]
: Jorge Villalobos [:jorgev]
Depends on:
  Show dependency treegraph
Reported: 2012-02-22 10:29 PST by Jorge Villalobos [:jorgev]
Modified: 2016-03-07 15:30 PST (History)
14 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Description Jorge Villalobos [:jorgev] 2012-02-22 10:29:27 PST
Versions older than of the McAfee Site Advisor add-on have serious memory leaks that can make Firefox unstable after extended periods of browsing. Versions and later should be used instead, and all current users should upgrade as soon as possible. This block is intended to warn users that they should upgrade to avoid problems.

We will asses the uptake of version next week (on the 29th) and decide if that's the right time to do the block.
Comment 1 Jorge Villalobos [:jorgev] 2012-02-29 08:14:20 PST
Davoud, can you please give us an update on the .195 uptake?
Comment 2 davoudm 2012-02-29 14:40:25 PST
Pretty much 90% of our entire user base has upgraded to Anyone installing 3.4 will be updated to in 24 hours. There is not that many users out there who will have this issue. So blocking older versions will most likely have not much effect since not many users are on it.
Comment 3 Nicholas Nethercote [:njn] 2012-02-29 15:13:43 PST
90% uptake is excellent, I'm glad to hear it.  But Site Advisor is popular enough that if 10% are on the old version that's still quite a lot of users.  So maybe a softblock is still worthwhile?  If we did softblock, is it possible to communicate to users that is available and mostly fixes the problems?
Comment 4 davoudm 2012-03-01 08:16:19 PST

I assure you that we are trying our best to increase this to 100%. But it is not as easy as there are partners and other issues involved in the process. Every day, there are more and more users on so this percentage is increasing every day. To be honest, I personally do not think that this is now as big of an issue as it was a week ago. A block of older siteadvisor versions may not even be necessary since the number of users moving  to is increasing daily. But this is your guys' call as there will always be some percentage of users who are behind and have not upgraded.
Comment 5 Jorge Villalobos [:jorgev] 2012-03-01 08:53:40 PST
I think we can do the block next week, to give remaining users some time to upgrade. It'll never be 100%, but we can help push you closer to that by warning users about it. A soft block gives users the option to continue using the add-on, so it isn't as problematic as a hard block. It should work as a good reminder that they need to upgrade their software asap.
Comment 6 Jorge Villalobos [:jorgev] 2012-03-08 13:23:26 PST
The block is now in place:

Users can still opt-out from the block, and upgrading to the latest version should also unblock the Site Advisor extension.
Comment 7 Kaz Nishimura 2012-04-16 19:10:25 PDT
The block list mentions version but I could not download any newer version than  Is the version number correct?
Comment 8 davoudm 2012-04-16 19:24:11 PDT
It says < .195

(In reply to Kaz Sasa from comment #7)
> The block list mentions version but I could not download any newer
> version than  Is the version number correct?
Comment 9 Masatoshi Kimura [:emk] 2012-04-16 21:24:26 PDT
Only the first occurrence says
> Who is affected?
>     All Firefox users who have installed the McAfee Site Advisor on Windows and 
> have a version older than
>     Versions and above should be unaffected by this block.
Comment 10 Jorge Villalobos [:jorgev] 2012-04-17 07:51:01 PDT
The description in the block said .915, but the block itself was correct (< .195). I corrected the description, and the block should be working correctly. We would have known if it had been wrong a long time ago.

Note You need to log in before you can comment on or make changes to this bug.