What changed in KB91697 (root cert) which was updated 8/12/2020

[ReallyWhy]

Does anyone know what information in this kb article changed?  

[cdinet]

Yes, please look at KB92953 and KB92937.

Some of our files were signed by the secondary cert AddTrust External CA Root that expired May 30 this year.  We had to change our files to be signed with a valid certificate (including dats/amcore content) to the primary USERTrust RSA Certification Authority.  So we no longer used the expired cert.  If the required root certificates are not in a customer environment, then there is no root certificate validation and things fail.  We give that KB for what we require to prevent any issues for when any certificate changes.  That also requires the latest agent msgbus cert updater package to be checked into the current branch of the repository.  You shouldn't have to do anything, as there is a default hidden task that runs at midnight to update any certs the agent uses.  

[ReallyWhy]

Thank you.  I have read through all of the KB articles and understand.  I updated systems with the .reg import manually last week.  We have also deployed the certs via GPO. 

So today when I received a notification from McAfee that KB91697 was updated, I need to know what portion of that article was updated.  Just trying to find out if action is needed on my part.  

Did the .bat or .reg file attachment to the previously posted KB article change since 6/17?    

Normally McAfee adds a revision table to their KB articles informing customers what has been changed, but in this KB they did not.  I am hoping you can help.  

Thanks!

[cdinet]

Ok now I understand your question better.  The only change that was made was to remove dlp 11.2 from the internal list of affected products since it is end of life.  It is nothing affecting the KB contents itself or the attachments.

[ReallyWhy]

I do not see DLPe in the "affected products" table, even as far back as 5/31/20.  It is listed in "products pending update" only.  So I'm still wondering what change was made to the KB article dated 8/12/20.  I think I will try to compare the .bat and .reg file just to be certain there weren't any changes made, because if there were, that would mean I (and all other McAfee customers) would need to reimport the .reg file or perhaps redeploy the GPO with the updated file. 

Thank you

[cdinet]

It is  not a change in the kb that customers will see, but an internal parameter that flags it for relevance to certain products and versions.  It is an internal only change.

[ReallyWhy]

Thank you for confirming it was something internal to McAfee that was changed.  That makes it difficult for the customers when they have signed up to receive subscription updates and are notified that a KB article has changed (but then cannot figure out what exactly changed). 

I did confirm that the attached files (.reg and .bat) were not changed.  

[ReallyWhy]

Is there any chance McAfee would add "internal only" when a KB article is marked as updated but does not include a revision table for the customer? I would think by doing so it would reduce the number of calls or questions raised to support teams. It would be helpful for the customers to know that nothing in the KB article changed that they need to be aware of. Thank you!

[cdinet · Accepted solution]

I can run that by the team, it is a good suggestion.

[ReallyWhy]

Awesome, thank you very much!