Messages

From another thread on this board I understand that PatchMyPC's stance regarding Firefox ESR is that only the "older" ESR build will be deployed/patched (https://patchmypc.com/forum/index.php?topic=5891.msg14510#msg14510).  While I understand your rational, we are having an issue because Mozilla is not updating the older ESR in accordance to what they said they will do.  To clarify based on this site Mozilla says they will back port high security updates to the older build:

https://support.mozilla.org/en-US/kb/firefox-esr-release-cycle

However, they are not doing that.  In July a high (8. CVE (https://nvd.nist.gov/vuln/detail/CVE-2023-3600#range-9419430) was announced impacting all versions of Firefox.  To date they have only provided an update for the 115 build of ESR.  All of our installs are being reported as vulnerable to the CVE from Qualys despite being on the latest 102 build.

So is there any chance PMPC will start to support both the older and newer ESR deployment?  Our only other alternative here is to block/remove Firefox ESR from our environment as Mozilla's failure to update high security vulnerabilities isn't tenable.

Thanks

That makes sense.  Thanks for the quick reply!

We bring in "R for Windows" but PMPC does not seem to be aware of version 4.2.0 that was released in April.

https://cran.r-project.org/bin/windows/base/old/

It it only bringing in 4.1.13 and that is the only version I see mentioned in the PatchMyPC.log.  I also don't see 4.2.0 being mentioned in the Catalog Updates so I don't think its our agent that is the issue.

Thanks!

Interesting.  Thanks Andrew.  We'll see how it goes next month now that I've added the auto-close option.  Maybe we've been lucky to not see it until now based on how old some of those reported issues are on github.

Thanks

Hello,

I'm 0 for 2 on testing Visual Studio Code 1.48.0 (x64) installs if Visual Studio Code is currently running.  Both computers were trying to upgrade from 1.47.X versions.  After the failed upgrade VSC is left in a broken state and throws the error shown in the screenshot when trying to launch (Uncaught Exception JavaScript error).  Attempting to install the update again does not fix the issue.  An install of the download directly from MS does fix it. 

The install seems to have worked on a computer where VS Code was not running at the time.  I have never included the "auto close" option in the past for VSC and it has always worked upgrading over top of a running instance.  So I'm not sure if MS has changed anything with the 1.48.0 version or not.  For now I've switched PMPC to "auto close" VSC and will test again when a new version of VSC releases - I've pulled the update for this months patches.

Thanks