GDLauncher VS Log4jAttackSurface

I used to use GDLauncher, but I would not recommend installing a launcher that lets issues like this one go by for almost a year without being fixed: https://github.com/gorilla-devs/GDLauncher/issues/1288

Skip all that manual install crap - https://prismlauncher.org/wiki/ or https://support.curseforge.com/en/support/solutions/articles/9000196904-creating-a-custom-profile or https://github.com/gorilla-devs/GDLauncher/wiki

Another way to make it easy, a bit less easy than the prior but a bit more customization - https://github.com/gorilla-devs/GDLauncher/wiki

The latest GDLauncher beta added an option to allow users to manually download problematic mods. You can get it here (click the Assets dropdown) or wait a few days for it to be released as a stable version.

I would have recommended GDLauncher until this happened to me last week: https://github.com/gorilla-devs/GDLauncher/issues/1288

Maybe give a different launcher a try, I use GDLauncher to run modpacks

maybe you could try GDlauncher it allows you to

Personally i use GdLauncher since it's really simple to use, it also automatically installs open jdk for you, something that basically makes the game run better than normal java, and can still manually download mods that have third-party downloads disabled.

Which other launchers could I use instead? – The shunted devs have established PlaceholderMC as a temporary official replacement. There's also ATLauncher, GDLauncher, and PolyMC itself was a fork of MultiMC.

Checkout this link for knowing Log4j impact on manufacturers https://github.com/YfryTchsGD/Log4jAttackSurface

Just look at the currently ongoing insanity that is the log4j exploit, and how one single exploit has lead to a generic attack that can impact tons of companies. Imagine if a state decided to use voting machines, and someone found this style of exploit in the system.

Last week (Dec 9th) a major vulnerability was discovered in an open source logging project for Java called log4j. The vulnerability called Log4Shell would allow anyone to remotely run arbitrary code if they sent a message in the right format to the server. This is one of the worst attacks your system can be susceptible to and if you are interested in the technical details of the problem, here is an overview. The attack surface of Log4Shell is staggering, Amazon, Apple, Google, and the Apache Server are affected; it can almost not get bigger than this. We will see the real fallout of Log4Shell in the next weeks and months as right now servers worldwide are being scanned and prodded for this vulnerability.

Companies should verify they are not running any exposed Log4j Java code.  Here is a list of impacted 3rd party software for your reference.  If you find a server at risk, there are three potential ways to fix it as follows.

Looking for vendors/software on known lists like https://github.com/YfryTchsGD/Log4jAttackSurface

Blender ist nicht betroffen, #42

It does and was also affected by log4j.

Thanks, sure it isn't complete but it does contain some scary and surprising (at least when first reading, of course the really aren't) things like: https://github.com/YfryTchsGD/Log4jAttackSurface/blob/master/pages/UniFi.md

Apparently there's proof Steam along with many others are vulnerable.